Java4Shell (CVE-2026-114938): Base64 Payload Spraying Observed Against Real Jenkins Honeypots

Java4Shell (CVE-2026-114938): Base64 Payload Spraying Observed Against Real Jenkins Honeypots
Photo by jonakoh _ / Unsplash

Previdian Research | 19 November 2026

On 18 November 2026, attackers began spraying Java4Shell (CVE-2026-114938) payloads across Previdian's global honeypot network, primarily targeting our real Jenkins application honeypots.

Requests contained long, repetitive Base64 strings in HTTP Basic Authorization headers, consistent with attempts to trigger the Java memory-corruption vulnerability.

Our initial analysis of 32 HTTP responses identified 28 standard Jenkins 401 responses and four ordinary 302 redirects. We found no evidence of leaked heap memory, confirmed memory corruption or remote code execution.

We had not observed this matching spray before 18 November. So far, the activity appears consistent with opportunistic internet-wide spraying rather than targeted exploitation.

Research Overview

VulnerabilityCVE-2026-114938 (Java4Shell)
Observation Period18–19 November 2026 (UTC)
EvidenceProprietary Previdian honeypot telemetry
Initial Analysis32 HTTP responses
CVE-Tagged Activity9 requests from 6 source IPs
Primary TargetReal Jenkins application honeypots
AssessmentAttempted exploitation; no confirmed success

Key Findings

  • Early activity: Java4Shell-pattern requests first appeared in our telemetry on 18 November, shortly after public disclosure.
  • Real application targeting: Seven CVE-tagged requests targeted real Jenkins honeypots. Two additional requests reached Jira and Microsoft Exchange decoys.
  • No confirmed exploitation: The observed payloads were consistent with attempts to trigger Java4Shell, but we identified no evidence of successful memory corruption, information disclosure or RCE.

Investigation

What We Observed

The first matching request reached one of our real Jenkins application honeypots in the early hours of 18 November.

It targeted /api/ and contained an unusual Basic Authorization header.

A representative request:

GET /api/ HTTP/1.1
Host: [redacted]
User-Agent: Mozilla/5.0
Authorization: Basic AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Connection: close

Normal HTTP Basic authentication uses Base64 to encode a username and password.

Instead, this request contained a long, repetitive Base64 value with malformed padding, consistent with publicly documented Java4Shell trigger patterns.

The request received an HTTP 401 response.

Our initial investigation examined 32 HTTP responses:

HTTP ResponseCount
401 Unauthorized28
302 Redirect4
Total32

None of these responses established successful exploitation.

Further Honeypot Observations

Our CVE-specific telemetry recorded nine matching requests between 18 and 19 November.

ApplicationHoneypot TypeRequests
JenkinsReal application7
Atlassian JiraDecoy1
Microsoft ExchangeDecoy1

Eight requests returned HTTP 401 and one returned HTTP 302.

These nine records represent a separate analysis scope from the initial 32-response review. The overlap between the datasets has not been established.

The same general payload appeared against unrelated applications, including a Microsoft Exchange decoy that does not expose the vulnerable Java decoding path.

Several source IPs had also recently probed unrelated vulnerabilities across our network.

Observation Timeline

DateEvent
17 NovemberCVE added to Previdian Watch
17 NovemberJava security fixes released
18 NovemberFirst matching requests observed against real Jenkins honeypots
18 NovemberCVE added to Previdian's KEV feed
19 NovemberAdditional observations and Previdian virtual patch available

Previdian Watch users following the vulnerability were monitoring it before our first observed attempts and its subsequent addition to Previdian KEV.

Understanding Java4Shell

Java4Shell is a heap-based memory-corruption vulnerability affecting the hardware-accelerated Base64 decoder in certain OpenJDK and Oracle Java runtimes.

Malformed Base64 input can trigger an out-of-bounds memory write, potentially resulting in application crashes, information disclosure or remote code execution.

However, exploitation has several important prerequisites.

The application must run an affected Java version on an x86-64 processor supporting the required CPU features, including AVX-512 VBMI. The affected accelerated decoder must also be enabled, and attacker-controlled input must reach it.

Potential entry points include HTTP Basic authentication, encoded tokens and other application inputs that process Base64.

Simply running Java does not make an application remotely exploitable.

Researchers at Calif have demonstrated exploitation against several Java-based products, including Jenkins, Keycloak, Jira and Confluence.

Organizations should consult the Oracle advisory and CERT-EU guidance for affected versions and available fixes.

Indicators of Compromise

The following source IP addresses were observed sending Java4Shell-pattern requests to Previdian honeypots.

Source IPRequestsTarget
217.138.216[.]1452Real Jenkins
180.104.209[.]452Real Jenkins
66.232.121[.]1132Real Jenkins
45.13.212[.]2091Real Jenkins
81.180.92[.]611Jira decoy
31.76.87[.]521Exchange decoy

These IP addresses are observed request sources, not proof of compromise or attribution to specific threat actors.

The primary network indicator is a malformed HTTP Basic Authorization header containing a long, repetitive Base64 value with unusual padding.

Observed request paths included /, /api/ and /rest/api/2/myself.

Recommendations for Defenders

Identify affected runtimes. Inventory Java installations, including bundled runtimes used by Jenkins and other enterprise applications. Check Java versions and the required CPU capabilities.

Apply security updates. Upgrade affected Java runtimes using vendor-supported fixes. Restart affected services and redeploy containers containing vulnerable runtimes.

Use temporary mitigations. Where patching is delayed, the affected Base64 intrinsic can be disabled using the documented JVM workaround. See the Jenkins mitigation guidance for implementation details.

Monitor suspicious activity. Investigate malformed Base64 Authorization headers alongside JVM crashes, unexpected process restarts and application errors. A matching request is an investigation lead, not proof of compromise.

Consider virtual patching. Previdian has developed a virtual patch for the observed Basic Authorization pattern, available for AWS WAF, Cloudflare and ModSecurity. It provides temporary protection against that specific HTTP pattern, not every possible Java4Shell attack path.

Conclusion

Our investigation shows that Java4Shell-pattern requests began reaching internet-facing applications shortly after disclosure, primarily targeting real Jenkins honeypots.

The observed activity is consistent with opportunistic exploitation attempts, but we have not confirmed successful memory corruption or remote code execution.

Previdian continues to monitor the vulnerability for changes in attacker behavior and evidence of successful exploitation.

For the latest intelligence, IoCs and defensive guidance, visit Previdian's CVE-2026-114938 record.

Know when exploitation starts.

Previdian monitors real-world exploitation activity to help security teams identify threats earlier and act with evidence.

Request a Demo