dssrf has an SSRF bypass with remove_at_symbol_in_string — GHSA-CG4G-M8JX-VJV2

Summary

## 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: ```ts u = remove_at_symbol_in_string(u); // strips ALL '@' from the raw string // ... const…

Timeline

Published by source

2026-07-30

Risk context

• Reported severity or threat level: high.
• Review exposure for the affected product or family: npm: dssrf.

Product

npm: dssrf

What to do

General, cautious steps (verify details in the official source):

• Prioritize patching or mitigation immediately (treat as actively risky).
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source
• CVE Record
• NVD

Evidence and provenance

Canonical advisory ID

GHSA-CG4G-M8JX-VJV2

Source

GitHub

Vendor

GitHub

Published by source

2026-07-30

Last source activity

2026-07-30

Additional identifiers

CVE-2026-54722

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.