`CVE-2026-55552`

Severity	7.5 High CVSS 3.1
Fixed in	`5.12.0`
Weakness	Path traversal (CWE-22)
Published	28 Aug 2026
Updated	8 Sep 2026

Published 2 months ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The 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.

Exploitation status

Working exploit published

A reviewed exploit catalogue lists ready-to-run exploit code for this CVE.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC 1 indexed Published artifacts you can open, in Nuclei.
EPSS 1.7% chance in 30 days

Index	Artifact	Stars	First seen
Nuclei	Yamcs <=5.11.12 - Arbitrary File Read

Index

Artifact

Stars

First seen

Nuclei

Yamcs <=5.11.12 - Arbitrary File Read

Waratek protection

Protected by Waratek

Waratek has a rule that blocks attacks on this vulnerability.

Protection full Path traversal
Action available security rule
Review automated Inferred
Record active

Decided by	A vulnerability class already blocked by an ARMR security rule
Finding	Protected by Waratek's ARMR path-traversal security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-22: Path Traversal.
Candidate fix	https://github.com/yamcs/yamcs/commit/c7dfd24e469ae1086c23e0fe04401cb1ce4260d4 : a commit: the change itself

Decided by

A vulnerability class already blocked by an ARMR security rule

Finding

Protected by Waratek's ARMR path-traversal security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-22: Path Traversal.

Candidate fix

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

How to mitigate CVE-2026-55552

Upgrade the affected software to 5.12.0 or later. Until you can, Waratek RASP blocks exploitation with its path traversal rule. It runs inside the Java application, with no code changes.

Waratek RASP Runtime protection for Java applications

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.yamcs:yamcs-core 0 5.12.0 unbounded

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

Products and versions

1 product, 1 version entry

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	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.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

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 JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: org.yamcs:yamcs-core

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

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

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

13 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.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

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

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

disposition: What do we do about one that is? every rule runs

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

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

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

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

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

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

24 no-exploit-published skipped Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

NVD ↗ · CVE.org ↗