<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 17:29:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338474</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338474</link>
      <description>EUVD-2026-338474</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338474</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44596</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44596</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44596</guid>
    </item>
    <item>
      <title>GHSA-w5r6-mcgq-7pq4 — Yamcs has No Rate Limiting on Authentication Endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w5r6-mcgq-7pq4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.yamcs:yamcs-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The 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.&lt;/p&gt;
&lt;p&gt;This missing rate limiting vulnerability (CWE-307) significantly increases the risk of successful brute-force attacks.&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;**File:** `yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java`&lt;/p&gt;
&lt;p&gt;`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:&lt;/p&gt;
&lt;p&gt;```java
// AuthHandler.java — handleToken()
// No throttle, no failed attempt counter, no lockout
private void handleToken(HandlerContext ctx) {
    ...
    getSecurityStore().login(token).whenComplete((info, err) -&amp;gt; {
        // Directly attempts authentication with no rate check
    });
}
```&lt;/p&gt;
&lt;p&gt;This is absent by default — the official quickstart and documentation contain no guidance on configuring rate limiting.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can make unlimited authentication attempts against any account. This enables efficient brute-force attacks against any account.&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```bash
# 20 attempts — zero rate limiting
for i in $(seq 1 20); do
  curl -s -o /dev/null -w &amp;#34;Attempt $i: HTTP %{http_code}\n&amp;#34; \
    -X POST &amp;#34;http://TARGET:8090/auth/token&amp;#34; \
    -d &amp;#34;grant_type=password&amp;amp;username=operator&amp;amp;password=op…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.yamcs:yamcs-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The 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.&lt;/p&gt;
&lt;p&gt;This missing rate limiting vulnerability (CWE-307) significantly increases the risk of successful brute-force attacks.&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;**File:** `yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java`&lt;/p&gt;
&lt;p&gt;`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:&lt;/p&gt;
&lt;p&gt;```java
// AuthHandler.java — handleToken()
// No throttle, no failed attempt counter, no lockout
private void handleToken(HandlerContext ctx) {
    ...
    getSecurityStore().login(token).whenComplete((info, err) -&amp;gt; {
        // Directly attempts authentication with no rate check
    });
}
```&lt;/p&gt;
&lt;p&gt;This is absent by default — the official quickstart and documentation contain no guidance on configuring rate limiting.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can make unlimited authentication attempts against any account. This enables efficient brute-force attacks against any account.&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```bash
# 20 attempts — zero rate limiting
for i in $(seq 1 20); do
  curl -s -o /dev/null -w &amp;#34;Attempt $i: HTTP %{http_code}\n&amp;#34; \
    -X POST &amp;#34;http://TARGET:8090/auth/token&amp;#34; \
    -d &amp;#34;grant_type=password&amp;amp;username=operator&amp;amp;password=op…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w5r6-mcgq-7pq4</guid>
    </item>
  </channel>
</rss>
