NationalSecurityAgency/emissary: Incomplete fix for CVE-2026-35571: SSRF
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 8.51.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.51.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Emissary, a peer-to-peer workflow engine, accepts protocol-relative URLs in its navigation links, which browsers can treat as links to external sites. An attacker with high privileges over the network, and with a user's interaction, could use this to redirect users or trigger server-side requests to external hosts, including cloud metadata.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Emissary is a P2P based data-driven workflow engine. Prior to 8.51.0, the VALID_LINK validation in src/main/java/emissary/server/mvc/NavAction.java accepts protocol-relative URLs when processing configured navigation links. Browser URL normalization can interpret these accepted strings as external origins. The authoritative advisory attributes open redirect, server-side request forgery, and cloud metadata access to this bypass, but it identifies neither the server-side dereference path nor how navigation-link processing reaches that path. This issue is fixed in version 8.51.0.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 52 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.51.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- NationalSecurityAgency emissary
fixed in 8.51.0
- gov.nsa.emissary:emissaryMaven
fixed in 8.51.0
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54442
Is CVE-2026-54442 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-54442?
emissary: before 8.51.0. gov.nsa.emissary:emissary (Maven): before 8.51.0.Source: cve.now feed data
How do I fix CVE-2026-54442?
Upgrade to a fixed version: 8.51.0.Source: cve.now feed data