CVE-2026-35583: Emissary has a Path Traversal via Blacklist Bypass in Configuration API

CVE-2026-35583 · Severity: medium · CVSS 5.3 · Published 2026-04-07

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.

Technologies: gov.nsa.emissary:emissary (Maven), Nsa Emissary. Vendors: Maven, Nsa.

Quick answers

Is CVE-2026-35583 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-35583 being exploited in the wild.
How severe is CVE-2026-35583?
Medium severity, with a CVSS score of 5.3, published 7 April 2026.
Which products and versions are affected?
gov.nsa.emissary:emissary (Maven) ECOSYSTEM:introduced=0,fixed=8.39.0.
Is there a fix for CVE-2026-35583?
Yes. gov.nsa.emissary:emissary (Maven): upgrade to 8.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-35583?
Check whether you run gov.nsa.emissary:emissary (Maven) or Nsa Emissary at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • gov.nsa.emissary:emissary (Maven): upgrade to 8.39.0 or later
    # set gov.nsa.emissary:emissary to 8.39.0 in your pom.xml or build.gradle

Affected products

  • gov.nsa.emissary:emissary (Maven) ECOSYSTEM:introduced=0,fixed=8.39.0
  • Nsa Emissary

Identifiers

  • CVE-2026-35583
  • GHSA-hxf2-gm22-7vcm

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.