Zarro Technology · Security briefing

Today’s briefing covers newly published Java guidance and GitLab security updates. Inventory bundled runtimes as well as standalone installations, and prioritise internet-facing applications and systems holding deployment secrets.

1. Java: Base64 memory corruption on affected AVX-512 systems (Critical)

CVE-2026-114938

Impact

The Canadian Cyber Centre’s 17 November alert describes a Base64 heap overflow that can permit unauthenticated code execution where malicious data reaches affected Java processes on x86-64 hardware with AVX-512 VBMI. It reports no known active exploitation. Scope depends on runtime build, hardware and application data flow; not every Java deployment is exposed.

Checks and remediation

Inventory each application’s runtime vendor and full build, including containers and vendor-bundled Java. Apply the appropriate corrected build through Oracle’s November patch guidance or your runtime supplier. The alert lists affected Oracle SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus specified Java 8 and GraalVM builds. These are affected versions, not upgrade targets.

If patching is delayed, the Cyber Centre recommends considering this JVM flag to disable AVX-512 use. Apply through the application’s supported startup configuration, test compatibility and restart the affected process:

-XX:UseAVX=2

No campaign-specific IoCs are supplied. Review application crashes, unexpected child processes and unusual outbound activity as investigation leads; their absence does not establish safety.

Sources: Canadian Cyber Centre — scope, affected builds and mitigation · Oracle — November patch availability

2. GitLab: protected CI/CD variables and Kubernetes secrets at risk (High)

CVE-2026-18241 (8.2), CVE-2026-97187 (7.6)

Impact

GitLab’s 16 November release fixes an authenticated pipeline-authorisation race that can expose protected CI/CD variables and resources. It also fixes workspace authorisation that can expose Kubernetes Secrets from other namespaces in connected clusters. The notice does not establish active exploitation.

Checks and remediation

Upgrade self-managed CE/EE to 19.3.9, 19.4.8 or 19.5.6, or a later fixed release on the appropriate supported branch. The pipeline issue reaches back to 9.3; the workspace issue to 17.6, with branch-specific ranges in the notice. GitLab.com is patched and Dedicated customers need no action.

Review pipeline access, unexpected use of protected variables and Kubernetes secret-access telemetry. These are hunting leads, not published campaign IoCs. Where exposure is suspected, preserve evidence and rotate affected secrets. The release includes further security fixes; review the complete advisory when planning deployment.

Sources: GitLab — affected ranges, scores and fixes

Zarro Technology