CVE-2026-44596

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.1% (81st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-44956 (ENISA EUVD) · GHSA-w5r6-mcgq-7pq4 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.1%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.1%
EPSS %ILE
81st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

July 17, 2026

Advisory Details (5)

Auto-updated Oct 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

No Rate Limiting on Authentication Endpoint · Advisory · yamcs/yamcs · GitHub

https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4
GitHub release Patch Available

Yamcs 5.13.0

Patch available: yamcs/yamcs yamcs-5.13.0

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0
GitHub release Patch Available

Yamcs 5.12.7

Patch available: yamcs/yamcs yamcs-5.12.7

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7
GitHub commit

commit 64392df531fb (yamcs/yamcs)

Fix landed in yamcs/yamcs commit 64392df531fb — awaiting tagged release

https://github.com/yamcs/yamcs/commit/64392df531fbcbc65f19ee5724c4c23d289f49fc
GitHub commit

commit 309218c65168 (yamcs/yamcs)

Fix landed in yamcs/yamcs commit 309218c65168 — awaiting tagged release

https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83

Vendor Advisories for CVE-2026-44596(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.yamcs:yamcs-core0.29.3 ... 5.9.9 (165 versions)
  • every version up to 5.12.7: fixed in 5.12.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 145 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 19:40 UTCEG score recompute
  2. 2026-10-30 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  3. 2026-10-29 17:47 UTCEG score recompute
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  6. 2026-10-28 16:02 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  8. 2026-10-27 14:16 UTCEG score recompute
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  10. 2026-10-26 12:03 UTCEG score recompute
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  12. 2026-10-25 14:27 UTCEG score recompute
  13. 2026-10-25 10:13 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  15. 2026-10-24 08:26 UTCEG score recompute
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  17. 2026-10-23 06:41 UTCEG score recompute
  18. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  19. 2026-10-22 04:56 UTCEG score recompute
  20. 2026-10-21 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  21. 2026-10-21 03:07 UTCEG score recompute
  22. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  23. 2026-10-20 01:19 UTCEG score recompute
  24. 2026-10-19 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  25. 2026-10-18 23:33 UTCEG score recompute
Show 75 more
  1. 2026-10-18 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  2. 2026-10-18 03:39 UTCEG score recompute
  3. 2026-10-17 21:48 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  5. 2026-10-16 20:02 UTCEG score recompute
  6. 2026-10-16 16:42 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  7. 2026-10-15 17:36 UTCEG score recompute
  8. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  9. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  10. 2026-10-14 11:24 UTCEG score recompute
  11. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  12. 2026-10-13 09:38 UTCEG score recompute
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  14. 2026-10-12 16:05 UTCEG score recompute
  15. 2026-10-11 19:47 UTCEG score recompute
  16. 2026-10-11 17:01 UTCEG score recompute
  17. 2026-10-11 14:27 UTCEG score recompute
  18. 2026-10-11 13:48 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  19. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  21. 2026-10-08 17:12 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  22. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  26. 2026-10-03 19:51 UTCOSV refresh
  27. 2026-10-03 14:25 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  31. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  32. 2026-09-23 17:53 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  33. 2026-09-20 20:15 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  34. 2026-09-18 19:28 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  35. 2026-09-17 19:31 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  36. 2026-09-16 14:08 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  37. 2026-09-16 05:15 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  38. 2026-09-14 09:34 UTCEG score recompute
  39. 2026-09-13 16:47 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  40. 2026-09-12 15:01 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  41. 2026-09-11 20:10 UTCOSV refresh
  42. 2026-09-11 14:53 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  43. 2026-09-11 09:37 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  44. 2026-09-10 09:34 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  45. 2026-09-08 22:00 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  46. 2026-09-07 16:01 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  47. 2026-09-06 13:47 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  48. 2026-09-04 05:06 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  49. 2026-09-02 14:12 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  50. 2026-09-01 13:54 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  51. 2026-08-30 19:17 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  52. 2026-08-30 01:22 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  53. 2026-08-28 21:41 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  55. 2026-08-26 14:46 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  57. 2026-08-23 15:53 UTCEG score recompute
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  59. 2026-08-22 01:19 UTCEG score recompute
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  61. 2026-08-21 21:14 UTCEG score recompute
  62. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  63. 2026-08-20 17:56 UTCEG score recompute
  64. 2026-08-19 17:04 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  65. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  66. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  67. 2026-08-16 16:29 UTCEG score recompute
  68. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  69. 2026-08-16 03:00 UTCEG score recompute
  70. 2026-08-16 02:14 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  71. 2026-08-15 02:20 UTCEG score recompute
  72. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  73. 2026-08-14 01:39 UTCEG score recompute
  74. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  75. 2026-08-12 13:55 UTCEG score recompute

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-52605
    Published May 30, 2026

    YAMCS yamcs-core 5.12.7 - No Rate Limiting

    Open source ↗

Frequently asked(5)

What is CVE-2026-44596?
CVE-2026-44596 is a critical-severity vulnerability; its CVE record was published on May 27, 2026. 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…
When was the CVE record for CVE-2026-44596 published?
The CVE record for CVE-2026-44596 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-44596 actively exploited?
CVE-2026-44596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (81st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44596?
CVE-2026-44596 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-44596?
A fix for CVE-2026-44596 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44596 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44596

Explore →

Is Your Infrastructure Affected by CVE-2026-44596?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.