Summary
TerriaJS-Server has a domain validation bypass vulnerability in its proxy allowlist
Impact
A validation bug allows an attacker to proxy domains not explicitly allowed in the proxyableDomains configuration.
The validation only checks if a hostname ended with an allowed domain. This meant:
If example.com is allowed in proxyableDomains:
- ✅ example.com is allowed (correct)
- ✅ api.example.com is allowed (correct)
- ⚠️ maliciousexample.com is allowed (incorrect)
An attacker could register maliciousexample.com and proxy content through terriajs-server, bypassing proxy restrictions.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
All versions up to 4.0.2 are affected. Upgrade to 4.0.3 to address the vulnerability.
Frequently Asked Questions
- What is CVE-2026-27818? CVE-2026-27818 is a high-severity improper input validation vulnerability in terriajs-server (npm), affecting versions < 4.0.3. It is fixed in 4.0.3. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of terriajs-server are affected by CVE-2026-27818? terriajs-server (npm) versions < 4.0.3 is affected.
- Is there a fix for CVE-2026-27818? Yes. CVE-2026-27818 is fixed in 4.0.3. Upgrade to this version or later.
- Is CVE-2026-27818 exploitable, and should I be worried? Whether CVE-2026-27818 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27818 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27818? Upgrade
terriajs-serverto 4.0.3 or later.