`CVE-2026-44596` Yamcs

Affected software	Yamcs
Severity	9.8 Critical CVSS 3.1 2 scores
Fixed in	`5.12.7`
Weakness	CWE-307
Published	16 Jul 2026
Updated	17 Jul 2026

Description

Yamcs is a mission control framework. Prior to 5.12.7, the authentication endpoint POST /auth/token in yamcs-core, handled by yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java, lacked any rate limiting, account lockout, or failed-attempt throttling, so an unauthenticated remote attacker could perform unlimited password-guessing attempts against any user account, significantly increasing the risk of successful brute-force attacks. This issue is fixed in versions 5.12.7 and 5.13.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: poc CISA recorded that an exploit has been demonstrated. Automatable: yes, technical impact: partial.
Indexed PoC 2 indexed Published artifacts you can open, in Exploit-DB, GitHub PoC; first seen 2026-05-29.
EPSS 2.1% chance in 30 days

1 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

Index	Artifact	Stars	First seen
Exploit-DB	YAMCS yamcs-core 5.12.7 - No Rate Limiting		2026-05-30
GitHub PoC	YAMCS yamcs-core < 5.12.7 lacks rate limiting on POST /auth/token. An unauthenticated attacker can perform unlimited brute-force attempts against any account. Never returns HTTP 429. Fixed in 5.12.7.		2026-05-29

Index

Artifact

Stars

First seen

Exploit-DB

YAMCS yamcs-core 5.12.7 - No Rate Limiting

2026-05-30

GitHub PoC

YAMCS yamcs-core < 5.12.7 lacks rate limiting on POST /auth/token. An unauthenticated attacker can perform unlimited brute-force attempts against any account. Never returns HTTP 429. Fixed in 5.12.7.

2026-05-29

Waratek protection

Mitigation candidate

A kind of vulnerability Waratek's rules address, with exploit code published or exploitation reported. No rule exists and none is planned yet. The decision below says what we found to build a rule from.

Protection none
Action unverified
Review automated Inferred
Record active

Decided by	A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug
Finding	A reference points at an upstream fix (commit tier): https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83. That makes this CVE a candidate for an ARMR patch rule — it is the kind of defect ARMR can address, and there is a fix to work from. No rule exists and none is scheduled: writing one means reading the linked change and finding a hook point ARMR can express it at, which may turn out not to exist.
Candidate fix	https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83 : a commit: the change itself

Decided by

A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

Finding

A reference points at an upstream fix (commit tier): https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83. That makes this CVE a candidate for an ARMR patch rule — it is the kind of defect ARMR can address, and there is a fix to work from. No rule exists and none is scheduled: writing one means reading the linked change and finding a hook point ARMR can express it at, which may turn out not to exist.

Candidate fix

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

CVSS

9.8 CRITICAL v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 9.8 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H NVD Primary published

CVSS 3.1 6.5 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N security-advisories@github.com Secondary

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

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

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

Products and versions

2 products, 2 version entries

Source	Vendor	Product	Scheme	Affected versions
osv	org.yamcs	yamcs-core	generic	＜ 5.12.7
nvd	spaceapplications	yamcs	generic	＜ 5.12.7

Source

Vendor

Product

Scheme

Affected versions

osv

org.yamcs

yamcs-core

generic

＜ 5.12.7

nvd

spaceapplications

yamcs

generic

＜ 5.12.7

References

URL	Tags
https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83	commit
https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4	WEB
https://github.com/yamcs/yamcs	PACKAGE
https://github.com/yamcs/yamcs/commit/64392df531fbcbc65f19ee5724c4c23d289f49fc	Patch
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7	Release Notes
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0	Release Notes

URL

Timeline

Published	2026-07-16	By the CVE Program.
NVD record modified	2026-07-17	NVD's own last-modified date for this record.

Published

2026-07-16

By the CVE Program.

NVD record modified

2026-07-17

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 decided it matched Mitigation candidate References include candidate fix URL (commit tier): https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83

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 no match A vulnerability class already blocked by an ARMR 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 no match Severity is CRITICAL — only MEDIUM/LOW are deprioritized

24 no-exploit-published no match A CISA or VulnCheck KEV listing, a CISA verdict of active exploitation, a reviewed exploit catalogue, or a GitHub PoC with 5 or more stars carries this CVE — exploit code is in use or published, so it stays a candidate

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

spaceapplications yamcs not tracked cpe:2.3:a:spaceapplications:yamcs:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗