Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-w789-49fc-v8hr

GHSA-w789-49fc-v8hr is a Improper Input Validation vulnerability in terriajs-server. O3 Security confirms whether GHSA-w789-49fc-v8hr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TerriaJS-Server has a domain validation bypass vulnerability in its proxy allowlist

Also known asCVE-2026-27818
Published
Feb 26, 2026
Updated
Feb 26, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

terriajs-servernpm
1Kdownloads / week

Description

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.

Patches

All versions up to 4.0.2 are affected. Upgrade to 4.0.3 to address the vulnerability.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmterriajs-serverall versions4.0.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for terriajs-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update terriajs-server to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w789-49fc-v8hr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-w789-49fc-v8hr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w789-49fc-v8hr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Patches All versions up to 4.0.2 are affected. Upgrade to 4.0.3 to address th
O3 Security · Impact-Aware SCA

Is GHSA-w789-49fc-v8hr in your dependencies?

O3 detects GHSA-w789-49fc-v8hr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.