<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T22:48:39.001536+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/certfr-2026-avi-1125</id>
    <title>certfr-2026-avi-1125 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-09-28T22:48:39.009116+00:00</updated>
    <content>certfr-2026-avi-1125</content>
    <link href="https://vulnerability.circl.lu/vuln/certfr-2026-avi-1125"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-67420</id>
    <title>fkie_cve-2026-67420</title>
    <updated>2026-09-28T22:48:39.009193+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ OAuth credential refresh retains revoked runtime tags. when an existing AMQP connection refreshes from an OAuth token that grants the impersonator tag to a valid same-username token that no longer grants that tag, RabbitMQ updates the OAuth backend implementation (token/scopes/expiry) but leaves the connection's runtime #user.tags unchanged. rabbitaccesscontrol:checkuserid/2 then still honors the stale impersonator tag, so the connection (including newly opened channels) can continue publishing messages with a foreign AMQP userid after that privilege should have been revoked. A fresh connection using the downgraded token correctly refuses the same publish, proving the defect is stale session state rather than the token Limited to connections that once held impersonator and successfully refresh to a downgraded same-username rabbitauthbackendoauth2 (or an equivalent refresh-capable backend that returns tags) is enabled for This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-67420"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:67552</id>
    <title>RHSA-2026:67552 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
    <updated>2026-09-28T22:48:39.009269+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rabbitmq-server: RabbitMQ: Unsanitized vhost names allow for XSS in management UI rabbitmq: RabbitMQ: Authenticated user can bypass connection limits via stream protocol rabbitmq: RabbitMQ: Information disclosure of decrypted Shovel URIs in debug logs rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters rabbitmq-server: RabbitMQ: Cross-Origin Resource Sharing (CORS) misconfiguration allows unauthorized actions rabbitmq-server: RabbitMQ: Denial of Service via atom table exhaustion in stream chunk_selector rabbitmq: RabbitMQ: Denial of Service via management API regular expression filter rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw rabbitmq: RabbitMQ: Information disclosure via cross-vhost authorization bypass RabbitMQ: RabbitMQ: Account takeover via stored Cross-Site Scripting in TLS peer-certificate DN rabbitmq-server: RabbitMQ: Denial of Service via AMQP 1.0 array32 parsing rabbitmq-server: RabbitMQ: Denial of Service via unbounded super-stream partition allocation rabbitmq-server: RabbitMQ: Privilege escalation via super-stream HTTP creation rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion rabbitmq: RabbitMQ: Information disclosure of AMQP 1.0 shovel URI passwords rabbitmq: RabbitMQ: Administrator path traversal allows arbitrary file write rabbitmq: RabbitMQ: Denial of Service vi…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:67552"/>
  </entry>
</feed>
