VulnerabilityPublished 30 Jul 2026

CVE-2026-54722: HackingRepo dssrf-js · Improper Neutralization of Equivalent Special Elements

Affects HackingRepo dssrf-jsSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.0.4 soon.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.4

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade HackingRepo dssrf-js to 1.0.4.

Affected software

Product	Affected	Fixed in
HackingRepodssrf-js	Affected <1.0.4	Fixed in 1.0.4
npmdssrf-js`pkg:npm/dssrf-js`Other threats	Affected <1.0.4	Fixed in 1.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade dssrf-js to version 1.0.4 or later, where this vulnerability is fixed. No other mitigation is specified or required as the fix addresses the root cause.

Description

CVE-2026-54722 is a high-severity vulnerability in the dssrf-js Node.js library prior to version 1.0.4. The issue involves improper neutralization of special elements in URL processing, specifically the '@' userinfo delimiter. This flaw allows an attacker to bypass internal IP validation checks, potentially causing a client to access internal services via crafted URLs. The vulnerability is fixed in version 1.0.4.

Impact

An attacker can craft URLs that bypass internal IP validation checks, potentially causing the client application to make unauthorized requests to internal services. This could lead to information disclosure or other impacts related to SSRF attacks. The CVSS 4.0 score is 8.7 (high), indicating a significant risk without requiring privileges or user interaction.

Summary

The dssrf-js library provides SSRF defense utilities for Node.js. Before version 1.0.4, the function is_url_safe in src/helpers.ts removes the '@' symbol from URLs before parsing them with the URL constructor. This removal allows attacker-controlled URLs to bypass internal IP validation, enabling Server-Side Request Forgery (SSRF) attacks that reach internal services. The vulnerability is identified as CWE-76 (Improper Neutralization of Equivalent Special Elements). The issue is resolved in dssrf-js version 1.0.4.

CWE-76Improper Neutralization of Equivalent Special Elements (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter equivalent special element syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 17:31 UTC

WeaknessesCWE-76

Technical details

References

Community reviews

Related threats