`CVE-2026-55552`

7.5 High Protected by RASP

Published 18 days ago. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.

Description

Yamcs is a mission control framework. Prior to 5.11.13, Yamcs StaticFileHandler.locateFile resolves an unauthenticated request path without using Path.normalize and Path.toAbsolutePath to confirm that the absolute path remains within the configured staticRoots. A path containing traversal segments can escape the intended web root and return an arbitrary readable host file. The flaw is in yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java and can disclose sensitive operating-system and application data. This issue is fixed in version 5.11.13, and the 5.12 line is fixed from version 5.12.0.

CWE-22 · Path traversal

Exploitation Status

No public exploit

Nothing published shows this CVE being exploited, which is not the same as ruling it out.

CVSS E:U

CISA KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC none indexed
EPSS 0.43% chance in 30 days

Waratek Defense Posture

Protected by RASP

A Waratek agent blocks this today.

Applicable rule: Promoted to MITIGATED-BY-RASP (security rule): this CVE's weakness (CWE-22: Path Traversal) can be mitigated by an ARMR path-traversal security rule that blocks this class of attack at the JVM level, without requiring a CVE-specific patch.

Protection full a general security rule for the vulnerability class
Action available security rule
Review automated inferred
Record active

Decided by secure-rule-match : A vulnerability class already blocked by an ARMR security rule

Finding Promoted to MITIGATED-BY-RASP (security rule): this CVE's weakness (CWE-22: Path Traversal) can be mitigated by an ARMR path-traversal security rule that blocks this class of attack at the JVM level, without requiring a CVE-specific patch.

Candidate fix https://github.com/yamcs/yamcs/commit/c7dfd24e469ae1086c23e0fe04401cb1ce4260d4 : a commit: the change itself

Decided by	`secure-rule-match` : A vulnerability class already blocked by an ARMR security rule
Finding	Promoted to MITIGATED-BY-RASP (security rule): this CVE's weakness (CWE-22: Path Traversal) can be mitigated by an ARMR path-traversal security rule that blocks this class of attack at the JVM level, without requiring a CVE-specific patch.
Candidate fix	https://github.com/yamcs/yamcs/commit/c7dfd24e469ae1086c23e0fe04401cb1ce4260d4 : a commit: the change itself

CVSS

7.5 HIGH v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 1 metric

VRT selects the newest version's highest entry and publishes it as cvssScore, newest rather than largest because scores are not comparable across versions, and highest rather than first because the first entry is frequently a CNA placeholder scoring 0.0 over NVD's own analysis.

Version Score Band Vector Assigner Type

CVSS 3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N security-advisories@github.com Secondary published

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	7.5	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`	security-advisories@github.com	Secondary	published

Affected Software & Releases

☕ Maven Library Packages

Artifact coordinates and fix boundaries from OSV.dev

Package Coordinate Introduced Fixed Last affected

org.yamcs:yamcs-core 0 5.12.0 unbounded

Package Coordinate	Introduced	Fixed	Last affected
`org.yamcs:yamcs-core`	0	`5.12.0`	unbounded

🖥️ Product CPEs & Version Ranges

1 product(s) over 1 version claims (uncapped)

Source	Vendor	Product	Scheme	Affected Versions
osv	org.yamcs	yamcs-core	generic	＜ 5.12.0

Source

Vendor

Product

Scheme

Affected Versions

osv

org.yamcs

yamcs-core

generic

＜ 5.12.0

References

URL	Tags
https://github.com/yamcs/yamcs/commit/c7dfd24e469ae1086c23e0fe04401cb1ce4260d4	commit
https://github.com/yamcs/yamcs/security/advisories/GHSA-9jg3-g3wh-w9pj	WEB
https://github.com/yamcs/yamcs/commit/f4bc588880c166849e983aa8f65b9c8107d06091	WEB
https://github.com/yamcs/yamcs	PACKAGE
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.11.13	WEB
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.0	WEB

URL

Timeline

Published 2026-08-28 Last modified 2026-09-08

Published	2026-08-28	By the CVE Program.
NVD record modified	2026-09-08	NVD's own last-modified date for this record.

Published

2026-08-28

By the CVE Program.

NVD record modified

2026-09-08

NVD's own last-modified date for this record.

Pipeline policy audit (15 of 21 rules evaluated)

15 of 21 rules ran. The rest were never reached, because an earlier stage settled the CVE, a distinct claim from a rule that ran and found nothing.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? first match wins

1 rejected no-match CVE Program withdrawal of this identifier

scope: Is the vulnerability ARMR's to address? first match wins

2 armr-patch-file no-match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no-match An ARMR security-rule template on disk for this CVE

4 manual-classification no-match A researcher's recorded decision for this specific CVE

5 manual classification no-match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no-match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no-match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the native WebLogic proxy plug-in. Oracle gives these no CPE of their own and names them only in the description.

8 osv-maven matched Queued for review Maven packages: org.yamcs:yamcs-core

9 cna-maven-package not-reached An affected Maven artifact named by the CNA itself

10 known-cpe-product not-reached An NVD CPE naming a product ARMR tracks

11 cna-cpe-product not-reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

12 oracle-advisory-family not-reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

13 non-deployable-product not-reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

14 unmatched-product not-reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? cumulative: every rule gets a turn

15 patch-hint matched Mitigation candidate References include candidate fix URL (commit tier): https://github.com/yamcs/yamcs/commit/c7dfd24e469ae1086c23e0fe04401cb1ce4260d4

16 open-source-maven skipped The affected package being open source on Maven, so the fix can be read

17 poc-derivable skipped An indexed exploit to reverse-engineer, where there is no source to read

18 no-exploit skipped With no fix path, a public exploit, or a CISA record of one

19 secure-rule-match decided it matched Protected by RASP CWE-22 (Path Traversal) is mitigable by an ARMR path-traversal security rule.

20 below-action-threshold skipped Medium or Low severity, no KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

21 no-exploit-published skipped A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all

Raw stored JSON document for this CVE ↗ · NVD ↗ · CVE.org ↗