<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T02:14:17.247991+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-101903</id>
    <title>fkie_cve-2026-101903</title>
    <updated>2026-10-01T02:14:17.275035+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Axios is a promise-based HTTP client for the browser and Node.js. From 1.16.1 until 1.20.0, the RFC 2397 regular expression allows slash characters on both sides of the media-type separator. An application passes an attacker-controlled malformed data URL containing many slash characters and no comma. the JavaScript regular-expression engine explores many separator placements before rejecting the URL. Synchronous excessive backtracking can block the Node.js event loop and cause denial of service. The affected identifiers are fromDataURI, DATA_URL_PATTERN, data:. This issue is fixed in version 1.20.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-101903"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-c29m-xwm3-cm6r</id>
    <title>GHSA-c29m-xwm3-cm6r — Axios: ReDoS in fromDataURI data: URL parser freezes the Node event loop (DoS)</title>
    <updated>2026-10-01T02:14:17.275087+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: axios</p>
<p>## Summary</p>
<p>Axios for Node.js parses `data:` URLs in `lib/helpers/fromDataURI.js`. The current RFC-2397 parser uses a regular expression whose media type groups allow `/` inside both sides of the `type/subtype` match. A malformed `data:` URL containing many slashes and no comma forces the JavaScript regex engine to try many possible placements for the separator before failing.</p>
<p>Applications are affected when they pass untrusted URL strings to axios and do not reject or constrain `data:` URLs before axios parses them.</p>
<p>## Impact</p>
<p>An attacker can make the Node.js event loop spend significant synchronous CPU time parsing a single malformed URL. In a server that accepts a URL from an HTTP request and calls `axios.get(url)`, this can block unrelated requests and health checks until parsing completes.</p>
<p>The issue is availability-only. It does not disclose data or modify requests.</p>
<p>## Affected Functionality</p>
<p>Affected:</p>
<p>- Node.js HTTP adapter data URL handling.
- `axios.get()` or equivalent calls where `config.url` has the `data:` protocol.</p>
<p>Not affected:</p>
<p>- Browser fetch/XHR URL handling.
- Node requests where the application rejects `data:` URLs before calling axios.
- Older checked `0.x` data URL parser shape unless separately proven vulnerable.</p>
<p>## Technical Details</p>
<p>`lib/helpers/fromDataURI.js` contains:</p>
<p>```js
const DATA_URL_PATTERN = /^([^,;]+\/[^,;]+)?((?:;[^,;=]+=[^,;]+)*)(;base64)?,([\s\S]*)$/;
```</p>
<p>The `[^,;]+` groups include `/`, so a long string of slashes without a comm…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-c29m-xwm3-cm6r"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-101903</id>
    <title>UBUNTU-CVE-2026-101903</title>
    <updated>2026-10-01T02:14:17.275168+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: node-axios, Ubuntu:Pro:22.04:LTS: node-axios, Ubuntu:Pro:24.04:LTS: node-axios, Ubuntu:Pro:26.04:LTS: node-axios</p>
<p>Axios is a promise-based HTTP client for the browser and Node.js. From 1.16.1 until 1.20.0, the RFC 2397 regular expression allows slash characters on both sides of the media-type separator. An application passes an attacker-controlled malformed data URL containing many slash characters and no comma. the JavaScript regular-expression engine explores many separator placements before rejecting the URL. Synchronous excessive backtracking can block the Node.js event loop and cause denial of service. The affected identifiers are fromDataURI, DATA_URL_PATTERN, data:. This issue is fixed in version 1.20.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-101903"/>
  </entry>
</feed>
