<?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-07T15:49:54.426011+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-252553</id>
    <title>EUVD-2026-252553</title>
    <updated>2026-10-07T15:49:54.488943+00:00</updated>
    <content>EUVD-2026-252553</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-252553"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-59058</id>
    <title>fkie_cve-2025-59058</title>
    <updated>2026-10-07T15:49:54.489002+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>httpsig-rs is a Rust implementation of IETF RFC 9421 http message signatures. Prior to version 0.0.19, the HMAC signature comparison is not timing-safe. This makes anyone who uses HS256 signature verification vulnerable to a timing attack that allows the attacker to forge a signature. Version 0.0.19 fixes the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-59058"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q7pg-9pr4-mrp2</id>
    <title>GHSA-q7pg-9pr4-mrp2 — httpsig-rs: HMAC verification is vulnerable to timing attack</title>
    <updated>2026-10-07T15:49:54.489040+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: httpsig</p>
<p>### Summary
HMAC signature comparison is not timing-safe and is vulnerable to timing attacks.</p>
<p>### Details
`SharedKey::sign()` returns a `Vec&lt;u8&gt;` which has a non-constant-time equality implementation.</p>
<p>`Hmac::finalize()` returns a constant-time wrapper ([`CtOutput`](https://docs.rs/digest/0.10.7/digest/struct.CtOutput.html)) which was discarded. Alternatively, `Hmac` has a constant-time `verify()` method.</p>
<p>The problem reported here is due to the following lines in `SharedKey::sign()` of the previous code:
```rust
let mut mac = HmacSha256::new_from_slice(key).unwrap();
mac.update(data);
Ok(mac.finalize().into_bytes().to_vec())
```
and the merged update changes the third line to directly verify with `verify_slice`.</p>
<p>### Impact</p>
<p>Anyone who uses HS256 signature verification is vulnerably to Timing Attack that allows the attacker to forge a signature.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q7pg-9pr4-mrp2"/>
  </entry>
</feed>
