Authenticated SSRF via unresolved internal hostnames
Published Mar 27, 2026 · Updated Mar 27, 2026
SSRF in LinkAce before 2.5.3 allows remote authenticated users to access internal HTTP services through application-side requests. NoPrivateIpRule rejects private IP literals but does not resolve and validate hostnames before HtmlMeta and FetchController fetch their destinations. Any authenticated account that submits an internal hostname can make the server retrieve otherwise unreachable content, exposing internal endpoints and responses.
Summary
What happened
SSRF in LinkAce before 2.5.3 allows remote authenticated users to access internal HTTP services through application-side requests. NoPrivateIpRule rejects private IP literals but does not resolve and validate hostnames before HtmlMeta and FetchController fetch their destinations. Any authenticated account that submits an internal hostname can make the server retrieve otherwise unreachable content, exposing internal endpoints and responses.
The record
- CVE
- CVE-2026-33953
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Kovah
- Product
- LinkAce
- Classifications
- CWE-918, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=< 2.5.3
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.
Public exploit references
- GHSA-wp4g-qw9j-wfjg reproduction procedureproof 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