<?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-10-01T15:15:17.538543+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/cve-2026-86219</id>
    <title>CVE-2026-86219 — Authen::SASL::Perl::DIGEST_MD5 versions before 2.2100 for Perl accept replayed authentication responses via unverified…</title>
    <updated>2026-10-01T15:15:17.645913+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Authen-SASL</p>
<p>Authen::SASL::Perl::DIGEST_MD5 versions before 2.2100 for Perl accept replayed authentication responses via unverified nonce in server_step.</p>
<p>server_start generates a fresh nonce and sends it in the challenge, and nothing later compares that value against the nonce the client returns. server_step derives the expected digest from the client's own parameters, so a response verifies whenever its digest matches the nonce it carries. The count table it also checks is keyed on the client-supplied nonce and starts empty in each new server object, so a captured first response, carrying `nc=00000001`, passes that too. RFC 2831 defines the nonce in the response as the value the server sent in the preceding challenge.</p>
<p>An attacker who observes one successful `qop=auth` exchange can replay the captured response against a later session for the same service, host, realm and user, and authenticate as that user without knowing the password.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-86219"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8858-1</id>
    <title>USN-8858-1 — libauthen-sasl-perl vulnerability</title>
    <updated>2026-10-01T15:15:17.646045+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libauthen-sasl-perl, Ubuntu:Pro:16.04:LTS: libauthen-sasl-perl, Ubuntu:Pro:18.04:LTS: libauthen-sasl-perl, Ubuntu:Pro:20.04:LTS: libauthen-sasl-perl, Ubuntu:22.04:LTS: libauthen-sasl-perl, Ubuntu:24.04:LTS: libauthen-sasl-perl, Ubuntu:26.04:LTS: libauthen-sasl-perl</p>
<p>It was discovered that Authen::SASL, a Perl authentication library, did
not properly validate login attempts. An attacker could possibly use
this issue to gain unauthorized access.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8858-1"/>
  </entry>
</feed>
