<?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-28T15:47:22.025637+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/fkie_cve-2026-67242</id>
    <title>fkie_cve-2026-67242</title>
    <updated>2026-09-28T15:47:23.463593+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, OAuth2 isinteger(Exp) guard skips token-expiry checks for float exp. validatetokenexpiry/1 (lines 208-214) and expirytimestamp/1 (138-144) both guard with 'when isinteger(Exp)' and fall through to ok/never for float values. josejwt:verify validates only the signature, not exp. With float exp, no expiry validation occurs anywhere in the If the IdP emits exp as a JSON float (RFC 7519 permits fractional NumericDate), both the login-time expiry check and the mid-connection disconnect timer are silently skipped , an already-expired token is accepted, and connections never time OAuth2 backend enabled IdP emits float exp (uncommon; mainstream IdPs emit integers) Attacker possesses a previously-valid signed. This issue is fixed in versions 4.2.9 and 4.3.3.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-67242"/>
  </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-28T15:47:23.463695+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>
