CVE-2026-44596

Yamcs: No Rate Limiting on Authentication Endpoint

Published Jul 16, 2026 CVSS 3.1 · 6.5 Medium EPSS 2.1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Yamcs is a mission‑control framework. In earlier releases before 5.12.7, the authentication endpoint POST /auth/token in the yamcs-core module does not enforce rate limiting, account lockout, or failed‑attempt throttling, allowing an unauthenticated remote attacker unlimited password‑guessing attempts against any user account, thereby significantly increasing the risk of successful brute‑force attacks.

Affected Systems

Affected products are Yamcs core libraries, particularly the authentication component in yamcs-core. The vulnerability exists in version 5.12.6 and earlier releases; it is fixed in releases 5.12.7 and 5.13.0.

Risk and Exploitability

The CVSS base score of 6.5 indicates a medium severity. The EPSS score of 2% suggests a modest but non‑negligible exploitation likelihood. The lack of rate limiting makes the attack surface readily exploitable. The vulnerability is not listed in CISA KEV, so organizations should consider patching promptly. An attacker can exploit the endpoint over the network without authentication, performing arbitrary login attempts until a correct credential is found.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Yamcs to version 5.12.7 or later
  • Restrict access to the authentication endpoint to trusted IP ranges using firewall or reverse proxy rules
  • Implement additional layer‑level rate limiting or account lockout controls for added defense

Generated by OpenCVE AI on July 31, 2026 at 01:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-w5r6-mcgq-7pq4 Yamcs has No Rate Limiting on Authentication Endpoint
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Yamcs
Yamcs yamcs
Vendors & Products Yamcs
Yamcs yamcs
Type Values Removed Values Added
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.
Title Yamcs: No Rate Limiting on Authentication Endpoint
Weaknesses CWE-307
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 2:05 PM
Reserved
May 6, 2026, 9:49 PM
Status
Analyzed
Published
Jul 16, 2026, 5:16 PM
Modified
Jul 17, 2026, 6:44 PM