<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 17:53:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-62985</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-62985</link>
      <description>&lt;p&gt;request-filtering-agent is an http(s).Agent implementation that blocks requests to Private/Reserved IP addresses. Prior to 3.2.1, RequestFilteringHttpAgent and RequestFilteringHttpsAgent synchronously threw from createConnection when rejecting a literal private-IP host such as 169.254.169.254 or 127.0.0.1. Because Node.js http.request and http.get expect connection failures to be delivered asynchronously, the throw bypassed req.on(&amp;#39;error&amp;#39;) and became an uncaught exception that could terminate the application process. Hostnames resolved through the asynchronous lookup path were not affected by this error-delivery asymmetry. This issue is fixed in version 3.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;request-filtering-agent is an http(s).Agent implementation that blocks requests to Private/Reserved IP addresses. Prior to 3.2.1, RequestFilteringHttpAgent and RequestFilteringHttpsAgent synchronously threw from createConnection when rejecting a literal private-IP host such as 169.254.169.254 or 127.0.0.1. Because Node.js http.request and http.get expect connection failures to be delivered asynchronously, the throw bypassed req.on(&amp;#39;error&amp;#39;) and became an uncaught exception that could terminate the application process. Hostnames resolved through the asynchronous lookup path were not affected by this error-delivery asymmetry. This issue is fixed in version 3.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-62985</guid>
    </item>
    <item>
      <title>GHSA-r3r9-wp5j-pq5g — request-filtering-agent: Synchronous throw from createConnection() for literal private-IP hosts bypasses req.on('error'…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-r3r9-wp5j-pq5g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: request-filtering-agent&lt;/p&gt;
&lt;p&gt;### Summary
`RequestFilteringHttpAgent` / `RequestFilteringHttpsAgent` block requests to private IPs, but the blocking happens via a **synchronous `throw`** inside `createConnection()` for literal private-IP hostnames (e.g. `169.254.169.254`, `127.0.0.1`). Node.js&amp;#39;s `http.request` / `http.get` expects `createConnection` to emit an error asynchronously; a synchronous throw instead escapes the caller&amp;#39;s `req.on(&amp;#39;error&amp;#39;, ...)` handler entirely and becomes an **unhandled exception** that crashes the process.&lt;/p&gt;
&lt;p&gt;### Affected
`request-filtering-agent` &amp;lt;= 3.2.0 (latest).&lt;/p&gt;
&lt;p&gt;### PoC (replicated live on 3.2.0)
```js
const http = require(&amp;#39;http&amp;#39;);
const { RequestFilteringHttpAgent } = require(&amp;#39;request-filtering-agent&amp;#39;);
const agent = new RequestFilteringHttpAgent();
process.on(&amp;#39;uncaughtException&amp;#39;, e =&amp;gt; {
  console.log(&amp;#39;CRASH:&amp;#39;, e.message); // fires — process dies
});
const req = http.get({ hostname: &amp;#39;169.254.169.254&amp;#39;, port: 80, agent });
req.on(&amp;#39;error&amp;#39;, e =&amp;gt; { /* never reached for literal IPs */ });
```
Actual output:
```
request-filtering-agent@3.2.0 synchronous throw escaping error event:
UNCAUGHT EXCEPTION (process crash): DNS lookup 169.254.169.254(...) is not allowed. Because, It is private IP address.
*** CRASH CONFIRMED: createConnection throws sync, bypasses req.on(&amp;#34;error&amp;#34;) ***
```
Note: hostnames that resolve to private IPs (e.g. `localhost`) are handled via the async lookup path and correctly emit an error event — this asymmetry confirms the sync-throw is a defect.&lt;/p&gt;
&lt;p&gt;### Impact
Any…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: request-filtering-agent&lt;/p&gt;
&lt;p&gt;### Summary
`RequestFilteringHttpAgent` / `RequestFilteringHttpsAgent` block requests to private IPs, but the blocking happens via a **synchronous `throw`** inside `createConnection()` for literal private-IP hostnames (e.g. `169.254.169.254`, `127.0.0.1`). Node.js&amp;#39;s `http.request` / `http.get` expects `createConnection` to emit an error asynchronously; a synchronous throw instead escapes the caller&amp;#39;s `req.on(&amp;#39;error&amp;#39;, ...)` handler entirely and becomes an **unhandled exception** that crashes the process.&lt;/p&gt;
&lt;p&gt;### Affected
`request-filtering-agent` &amp;lt;= 3.2.0 (latest).&lt;/p&gt;
&lt;p&gt;### PoC (replicated live on 3.2.0)
```js
const http = require(&amp;#39;http&amp;#39;);
const { RequestFilteringHttpAgent } = require(&amp;#39;request-filtering-agent&amp;#39;);
const agent = new RequestFilteringHttpAgent();
process.on(&amp;#39;uncaughtException&amp;#39;, e =&amp;gt; {
  console.log(&amp;#39;CRASH:&amp;#39;, e.message); // fires — process dies
});
const req = http.get({ hostname: &amp;#39;169.254.169.254&amp;#39;, port: 80, agent });
req.on(&amp;#39;error&amp;#39;, e =&amp;gt; { /* never reached for literal IPs */ });
```
Actual output:
```
request-filtering-agent@3.2.0 synchronous throw escaping error event:
UNCAUGHT EXCEPTION (process crash): DNS lookup 169.254.169.254(...) is not allowed. Because, It is private IP address.
*** CRASH CONFIRMED: createConnection throws sync, bypasses req.on(&amp;#34;error&amp;#34;) ***
```
Note: hostnames that resolve to private IPs (e.g. `localhost`) are handled via the async lookup path and correctly emit an error event — this asymmetry confirms the sync-throw is a defect.&lt;/p&gt;
&lt;p&gt;### Impact
Any…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-r3r9-wp5j-pq5g</guid>
    </item>
  </channel>
</rss>
