Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-59392

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-59392
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-59392The repository contains a Java integration-test exploit, not merely documentation or a passive detector. Its seven files comprise one JUnit test source, pom.xml, Unix and Windows Maven launchers, wrapper properties, a README, and .gitignore. The three executable/code files are the Java test and two wrapper scripts; PowerShell appears inside the Windows wrapper. No exploitation framework is used. The test starts an embedded Spring application on an ephemeral port and connects three SockJS/STOMP clients over loopback. Separate principals receive session IDs victim123, *, and attacker123. All subscribe to /user/queue/private. The application sends PRIVATE-FOR-VICTIM using convertAndSendToUser("victim", "/queue/private", ...), and assertions require receipt by both the victim and wildcard attacker, but not the ordinary control session. This actively exercises unauthorized disclosure rather than checking a version string. The documented root cause crosses AbstractSockJsService, DefaultUserDestinationResolver, and DefaultSubscriptionRegistry: a client-controlled session identifier is accepted as an identifier, appended to a broker destination, and subsequently interpreted as an AntPathMatcher pattern. The attacker supplies a normal STOMP destination and need not guess the victim's session ID. The demonstrated impact is confidentiality loss; no code execution, message modification, persistence, or external exfiltration capability is implemented. Authentication is simulated by a test-only X-Test-User handshake header, so the example is not a production authentication implementation. The README reports Spring Framework 7.0.9 through Spring Boot 4.1.1; the POM explicitly selects Boot 4.1.1. No CVE is supplied, and affected-version coverage beyond the stated environment is not established. The hardcoded protocol payload is operational within this local test harness, but there is no arbitrary remote-target interface. Maven Central URLs belong to build bootstrapping, not command-and-control infrastructure. Analysis is static; successful execution was not independently verified. The original repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.daehyuh · Disclosed Sep 11, 2026 · java · sh · networkOperational
FAQ

Frequently asked questions

Is CVE-2026-59392 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-59392 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59392?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-59392, 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.