Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-35583: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in NationalSecurityAgency emissary

0
Medium
VulnerabilityCVE-2026-35583cvecve-2026-35583cwe-22
Published: Tue Apr 07 2026 (04/07/2026, 15:57:41 UTC)
Source: CVE Database V5
Vendor/Project: NationalSecurityAgency
Product: emissary

Description

Emissary is a P2P based data-driven workflow engine. Prior to 8.39.0, the configuration API endpoint (/api/configuration/{name}) validated configuration names using a blacklist approach that checked for \, /, .., and trailing .. This could potentially be bypassed using URL-encoded variants, double-encoding, or Unicode normalization to achieve path traversal and read configuration files outside the intended directory. This vulnerability is fixed in 8.39.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/15/2026, 12:24:47 UTC

Technical Analysis

Emissary, a P2P data-driven workflow engine by the NationalSecurityAgency, had a path traversal vulnerability (CWE-22) in versions before 8.39.0. The configuration API endpoint (/api/configuration/{name}) validated input using a blacklist that checked for characters like \, /, .., and trailing .., but this approach was bypassable using URL-encoded variants, double-encoding, or Unicode normalization. This flaw allowed attackers to access configuration files outside the intended directory. The vulnerability was addressed and fixed in version 8.39.0. The CVSS 3.1 base score is 5.3, reflecting a medium severity with network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality impact.

Potential Impact

An attacker can exploit this vulnerability remotely without authentication or user interaction to read configuration files outside the intended directory. This could lead to disclosure of sensitive configuration data. There is no impact on integrity or availability reported. No known exploits in the wild have been documented.

Mitigation Recommendations

This vulnerability is fixed in emissary version 8.39.0. Users should upgrade to version 8.39.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fix in 8.39.0, so confirm with the vendor advisory for the latest remediation guidance. No other mitigations are specified.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-03T20:09:02.827Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69d5314faaed68159a339928

Added to database: 4/7/2026, 4:31:11 PM

Last enriched: 4/15/2026, 12:24:47 PM

Last updated: 5/22/2026, 3:54:46 AM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses