Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-59398

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-59398
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-59398The repository contains a self-contained Java/JUnit resource-exhaustion demonstration, not an exploit-framework module. Its seven files comprise one Java test/application, a Maven POM, Unix and Windows Maven launchers, wrapper properties, a README, and .gitignore. PowerShell appears within the Windows launcher's dependency-download logic. The POM declares Spring Boot parent 4.1.1, WebFlux and test dependencies, and Java 17. The nested application enables opt-in parameter content negotiation and serves JSON at GET /probe. The test submits 10,000 sequential loopback requests with unique format values constructed from 1,000 padding characters, an index, and .json. ParameterContentTypeResolver resolves the final extension but caches the complete supplied value in its mediaTypes map. Consequently, otherwise equivalent JSON requests retain distinct large strings for the application lifetime. Reflection obtains the cache for observation; it does not insert the malicious keys. Assertions check HTTP 200 responses, JSON content types, exactly 10,000 additional entries, and over 10 million retained characters. This is active vulnerability reproduction rather than passive detection, but its hardcoded request count and loopback destination make it a bounded laboratory demonstration. It measures retained cache growth rather than proving immediate outage. No command-execution payload, persistence, credential access, or exfiltration is present. Maven Central URLs are build dependencies, not attacker infrastructure. The README reports testing WebFlux 7.0.9 and claims the same code exists in 6.2.19, 7.0.x, and main; those claims were not independently verified. No CVE is supplied. The documented weakness is CWE-770, and the suggested mitigation is to avoid caching dotted composite keys or remove the dynamic cache write. Analysis is based on the supplied source and was not execution-validated. The repository URL, Git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata. The listed file sizes total 25,191 bytes, which is not a measured archive size.daehyuh · Disclosed Sep 11, 2026 · java · sh · network · webOperational
FAQ

Frequently asked questions

Is CVE-2026-59398 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-59398 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59398?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-59398, the earliest disclosed Sep 11, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.