<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T15:00:20.450381+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-194934</id>
    <title>EUVD-2026-194934</title>
    <updated>2026-10-06T15:00:20.453078+00:00</updated>
    <content>EUVD-2026-194934</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-194934"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-37918</id>
    <title>fkie_cve-2023-37918</title>
    <updated>2026-10-06T15:00:20.453109+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. A vulnerability has been found in Dapr that allows bypassing API token authentication, which is used by the Dapr sidecar to authenticate calls coming from the application, with a well-crafted HTTP request. Users who leverage API token authentication are encouraged to upgrade Dapr to 1.10.9 or to 1.11.2. This vulnerability impacts Dapr users who have configured API token authentication. An attacker could craft a request that is always allowed by the Dapr sidecar over HTTP, even if the `dapr-api-token` in the request is invalid or missing. The issue has been fixed in Dapr 1.10.9 or to 1.11.2. There are no known workarounds for this vulnerability.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-37918"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-59m6-82qm-vqgj</id>
    <title>GHSA-59m6-82qm-vqgj — Dapr API token authentication bypass in HTTP endpoints</title>
    <updated>2026-10-06T15:00:20.453145+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/dapr/dapr</p>
<p>### Summary</p>
<p>A vulnerability has been found in Dapr that allows bypassing [API token authentication](https://docs.dapr.io/operations/security/api-token/), which is used by the Dapr sidecar to authenticate calls coming from the application, with a well-crafted HTTP request.</p>
<p>Users who leverage API token authentication are encouraged to upgrade Dapr to 1.10.9 and 1.11.2.</p>
<p>### Impact</p>
<p>This vulnerability impacts Dapr users who have configured API token authentication. An attacker could craft a request that is always allowed by the Dapr sidecar over HTTP, even if the `dapr-api-token` in the request is invalid or missing.</p>
<p>### Patches</p>
<p>The issue has been fixed in Dapr 1.10.9 and 1.11.2.</p>
<p>### Details</p>
<p>When API token authentication is enabled, Dapr requires all calls from applications to include the `dapr-api-token` header, with a value matching what's included in the Dapr's configuration. In order to allow for healthchecks to work, the `/v1.0/healthz` and `/v1.0/healthz/outbound` HTTP APIs are excluded from the API token authentication check, and are always allowed.</p>
<p>Dapr &lt;= 1.10.8 and &lt;= 1.11.1 implemented the allowlisting of the healthcheck endpoints by permitting all requests whose URL contains `/healthz` to bypass the API token authentication check. The match applied anywhere in the URL, including the querystring.</p>
<p>As a consequence, attackers were able to bypass API token authentication by including `/healthz` anywhere in the URL, including as a querystring parameter.…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-59m6-82qm-vqgj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-37918</id>
    <title>gsd-2023-37918</title>
    <updated>2026-10-06T15:00:20.453200+00:00</updated>
    <content>gsd-2023-37918</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-37918"/>
  </entry>
</feed>
