Internal service access via stripped userinfo delimiter
Published Jul 30, 2026 · Updated Jul 30, 2026
SSRF protection bypass in RelunSec dssrf before 1.0.4 allows remote attackers to reach internal services through crafted URLs. The is_url_safe path removes the @ userinfo delimiter before URL parsing, validates a corrupted hostname, and marks the attacker-supplied URL safe. Exposure requires a consuming application to validate attacker-controlled input and then request the original URL, enabling access to internal endpoints.
Summary
What happened
SSRF protection bypass in RelunSec dssrf before 1.0.4 allows remote attackers to reach internal services through crafted URLs. The is_url_safe path removes the @ userinfo delimiter before URL parsing, validates a corrupted hostname, and marks the attacker-supplied URL safe. Exposure requires a consuming application to validate attacker-controlled input and then request the original URL, enabling access to internal endpoints.
The record
- CVE
- CVE-2026-54722
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- RelunSec
- Product
- dssrf
- Classifications
- CWE-76, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cg4g-m8jx-vjv2 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo