CVE-2026-44596: Yamcs core Yamcs Has No Rate Limiting Vulnerability
MODERATECVE-2026-44596 is a MODERATE (CVSS 6.5) yamcs has no rate limiting vulnerability (CWE-307: Improper Restriction of Excessive Authentication Attempts) affecting Yamcs core libraries in the Maven ecosystem. The issue involves yamcs has no rate limiting on authentication endpoint. Remediation is available by upgrading affected packages to version 5.12.7.
CVE-2026-44596 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-44596
To remediate this vulnerability, upgrade all affected Yamcs core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.yamcs</groupId>
<artifactId>yamcs-core</artifactId>
<version>5.12.7</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.yamcs
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-44596, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.yamcs
Analyze the terminal output to locate any version of Yamcs core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.12.7), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.yamcs command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts, where the product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. In Yamcs core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-44596 Affected Yamcs core Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.yamcs:yamcs-core
|
Maven |
< 5.12.7
|
5.12.7
|
References
Frequently Asked Questions
What is CVE-2026-44596?
Which Yamcs core versions are affected?
What version fixes CVE-2026-44596?
Is yamcs-core affected?
What is the CVSS score of CVE-2026-44596?
What CWE is associated with CVE-2026-44596?
How can I check Maven dependencies for CVE-2026-44596?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-w5r6-mcgq-7pq4",
"modified" : "2026-05-27T00:04:28Z",
"published" : "2026-05-27T00:04:28Z",
"aliases" : [ "CVE-2026-44596" ],
"summary" : "Yamcs has No Rate Limiting on Authentication Endpoint",
"details" : "### Summary\n\nThe authentication endpoint `POST /auth/token` in `yamcs-core` lacks any form of rate limiting, account lockout, or failed attempt throttling. As a result, an unauthenticated remote attacker can perform unlimited password guessing attempts against any user account.\n\nThis missing rate limiting vulnerability (CWE-307) significantly increases the risk of successful brute-force attacks.\n\n### Root Cause\n\n**File:** `yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java`\n\n`POST /auth/token` has no rate limiting, no lockout after failed attempts, and no CAPTCHA. The handler processes unlimited authentication requests without any throttling mechanism:\n\n```java\n// AuthHandler.java — handleToken()\n// No throttle, no failed attempt counter, no lockout\nprivate void handleToken(HandlerContext ctx) {\n ...\n getSecurityStore().login(token).whenComplete((info, err) -> {\n // Directly attempts authentication with no rate check\n });\n}\n```\n\nThis is absent by default — the official quickstart and documentation contain no guidance on configuring rate limiting.\n\n### Impact\n\nAn attacker can make unlimited authentication attempts against any account. This enables efficient brute-force attacks against any account.\n\n### Proof of Concept\n\n```bash\n# 20 attempts — zero rate limiting\nfor i in $(seq 1 20); do\n curl -s -o /dev/null -w \"Attempt $i: HTTP %{http_code}\\n\" \\\n -X POST \"http://TARGET:8090/auth/token\" \\\n -d \"grant_type=password&username=operator&password=operator12$i\"\ndone\n# All return HTTP 401 — no HTTP 429 ever\n```\n\n**Confirmed:** 20 attempts in 0.07 seconds, no rate limiting enforced.\n\n### Fix\n\nImplement DRF-style throttling on `/auth/token`:\n\n```java\n// Track failed attempts per IP\nprivate static final Cache<String, Integer> FAILED_ATTEMPTS =\n CacheBuilder.newBuilder().expireAfterWrite(15, TimeUnit.MINUTES).build();\n\nprivate static final int MAX_ATTEMPTS = 10;\n\nprivate void handleToken(HandlerContext ctx) {\n String ip = ctx.getRemoteAddress();\n int attempts = Optional.ofNullable(FAILED_ATTEMPTS.getIfPresent(ip)).orElse(0);\n if (attempts >= MAX_ATTEMPTS) {\n throw new TooManyRequestsException(\"Rate limit exceeded\");\n }\n // ... existing auth logic\n // On failure: FAILED_ATTEMPTS.put(ip, attempts + 1)\n}\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.yamcs:yamcs-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.12.7"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/yamcs/yamcs"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-307" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-27T00:04:28Z",
"nvd_published_at" : null
}
}