<?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-07T01:44:51.078139+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-322105</id>
    <title>EUVD-2026-322105</title>
    <updated>2026-10-07T01:44:51.190188+00:00</updated>
    <content>EUVD-2026-322105</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-322105"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47067</id>
    <title>fkie_cve-2026-47067</title>
    <updated>2026-10-07T01:44:51.190228+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The URL parser in src/hackney_url.erl converts every unrecognized URL scheme to a permanent BEAM atom via binary_to_atom/2. BEAM atoms are never garbage-collected and the atom table defaults to a hard limit of 1,048,576 entries. An attacker who can supply URLs with attacker-chosen scheme prefixes — directly as request targets, as configured webhook URLs, or via Location headers followed during redirects — can exhaust the atom table and crash the entire BEAM VM with system_limit.</p>
<p>This issue affects hackney: from 2.0.0 before 4.0.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-47067"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9653-rcfr-5c62</id>
    <title>GHSA-9653-rcfr-5c62 — Hackney vulnerable to atom-table exhaustion via unrecognized URL schemes</title>
    <updated>2026-10-07T01:44:51.190274+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Hex: hackney</p>
<p>### Summary</p>
<p>[CVE-2026-47067](https://nvd.nist.gov/vuln/detail/CVE-2026-47067) is an atom table exhaustion vulnerability (CWE-770) in hackney's URL parser (`src/hackney_url.erl`). `hackney_url:parse_url/1` converts every URL scheme it encounters into a BEAM atom via `binary_to_atom/2`. Because BEAM atoms are never garbage-collected and the atom table has a hard limit of 1,048,576 entries, an attacker who can feed URLs with attacker-chosen scheme prefixes — directly as request targets, as webhook/callback URLs, or via `Location` headers in redirect chains — can exhaust the atom table and crash the entire BEAM VM with `system_limit`.</p>
<p>### Details</p>
<p>**1. Scheme extraction and conversion**</p>
<p>In `src/hackney_url.erl`, `parse_url/1` extracts the scheme binary (the part before `://`), validates it with `is_valid_scheme/1` (RFC 3986 alphabet: alpha-led, `&lt;=19` bytes, alphanumeric/`+`/`-`/`.` body), lowercases it, then calls:</p>
<p>```erlang
binary_to_atom(SchemeLower, utf8)
```</p>
<p>The resulting atom is stored on the `#hackney_url{}` record and returned to the caller.</p>
<p>**2. Permanent atom accumulation**</p>
<p>The validation constrains the alphabet but not uniqueness. The allowed scheme space is enormous (≈52·65¹⁸ values), far exceeding the default atom limit of 1,048,576. Each distinct scheme mints a new permanent atom. Even when hackney subsequently rejects an unsupported scheme with `{error, {unsupported_scheme, _}}`, the atom has already been interned and is never reclaimed.</p>
<p>**3. Crash vector*…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9653-rcfr-5c62"/>
  </entry>
</feed>
