<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-13T20:24:56.954568+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-124679</id>
    <title>CVE-2026-124679 — Apache APISIX: jwe-decrypt and forward-auth may pass a client-supplied identity header</title>
    <updated>2026-11-13T20:24:56.956171+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Apache Software Foundation Apache APISIX</p>
<p>Authentication bypass by spoofing vulnerability in Apache APISIX.</p>
<p>On routes using jwe-decrypt with strict: false and a
forward_header distinct from the token header an unauthenticated
client can supply the value the upstream treats as gateway-decrypted
plaintext. Similar can happen when forward-auth is configured with allow_degradation: true, and the auth service is unavailable.</p>
<p>This issue affects Apache APISIX: from 3.18.0 through 3.19.0.</p>
<p>Users are recommended to upgrade to version 3.20.0, which fixes the issue.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-124679"/>
  </entry>
</feed>
