← Back to Daily Briefing (#OpenJDK)

Java4Shell: OpenJDK CVE-2026-114938 RCE Exploited via ARTEX and Chrome User-Agent Spoofing

Published November 20, 2026

Threat actors are actively exploiting CVE-2026-114938 (Java4Shell), an OpenJDK remote code execution vulnerability. Cloudflare Cloudforce One observed a two-stage pattern: initial reconnaissance from a source IP using a scanner-identifying User-Agent, followed approximately 17 hours later by exploit attempts spoofing Google Chrome User-Agent headers. The ARTEX framework obfuscates payloads using Base64 encoding to evade signature-based detection. GreyNoise, WatchTowr, and Cloudflare confirmed probing and exploitation. Cisco, Elastic, Red Hat, and Siemens products are impacted. Vendors including Cisco, Microsoft, and Wiz have issued advisories, patches, and Azure WAF mitigations.

  • Vulnerability Overview: CVE-2026-114938 (Java4Shell)

    • OpenJDK remote code execution vulnerability under active exploitation in the wild.
    • Affects enterprise Java deployments and dependent vendor products broadly.
    • Confirmed impact on Cisco, Elastic, Red Hat, and Siemens product lines.
    • Exploitation attributed to unattributed actor(s) operating from a single source IP.
  • Exploitation Mechanics: Two-Stage Attack Pattern

    • Stage 1: Source IP scans targets with a User-Agent header that identifies the scanning tool.
    • Stage 2: ~17 hours later, exploit attempt returns with spoofed Chrome User-Agent to mimic legitimate browser traffic.
    • ARTEX component used for payload encoding and obfuscation, likely leveraging Base64.
    • Obfuscation bypasses simple string-matching and signature-based detection rules.
  • Impact and Telemetry: Active Exploitation Confirmed

    • Exploitation status: Active in the wild; probing and exploit attempts verified by multiple telemetry sources.
    • Telemetry sources: Cloudflare Cloudforce One, GreyNoise, WatchTowr.
    • Detection gap: 17-hour window between scan and exploit; Chrome spoofing complicates log-based detection.
    • Broad exposure across OpenJDK runtimes and downstream enterprise Java ecosystems.
  • Detection and Mitigation: Vendor Advisories and WAF Patching

    • Cisco, Microsoft Azure, Wiz, and others released advisories with upgrade guidance and patches.
    • Azure WAF mitigations available for virtual patching of unpatched OpenJDK instances.
    • Prioritize OpenJDK upgrades and apply vendor-specific patches immediately.
    • Hunt for ARTEX/Base64-encoded payloads and anomalous Chrome traffic from unexpected sources.
  • Conclusion: Immediate Action Required

    • Treat CVE-2026-114938 as actively exploited; assume exposure in Java-facing infrastructure.
    • Deploy WAF rules and patch OpenJDK to close the remote code execution vector.
    • Monitor for scanner User-Agent leaks and 17-hour scan-to-exploit recurrence patterns.

Related posts

  1. Cybersecurity News — Hackers Exploiting Java4Shell RCE Flaw Using ARTEX Disguise Themselves as Chrome
  2. blackhatnews.tokyo — Java4Shell の重大な脆弱性、人気の Java サーバーでリモートからコードを実行される恐れ
  3. hackernews.com — Java4Shell: RCE in OpenJDK when processing Base64
  4. Security
  5. Blog
  6. Wiz
  7. Sec
  8. Esri
  9. Techcommunity
  10. Hackaday
  11. SecurityWeek — Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories

LINK COPIED TO CLIPBOARD