Unauthenticated SSRF via suffix-only hostname validation
Published Feb 26, 2026 · Updated Feb 26, 2026
SSRF in the proxy controller in TerriaJS-Server before 4.0.3 allows remote attackers to relay requests to disallowed domains. The allowlist test accepts any hostname ending with an allowed domain, so attacker-controlled maliciousexample.com matches example.com without a dot boundary. Network access to the proxy endpoint and a configured allowed domain are required; successful exploitation turns the server into an unauthorized relay to the attacker-controlled host.
Summary
What happened
SSRF in the proxy controller in TerriaJS-Server before 4.0.3 allows remote attackers to relay requests to disallowed domains. The allowlist test accepts any hostname ending with an allowed domain, so attacker-controlled maliciousexample.com matches example.com without a dot boundary. Network access to the proxy endpoint and a configured allowed domain are required; successful exploitation turns the server into an unauthorized relay to the attacker-controlled host.
The record
- CVE
- CVE-2026-27818
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Terria
- Product
- TerriaJS-Server
- Classifications
- CWE-20, CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=< 4.0.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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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