Vulnerability in @orpc/server (CVE-2026-77360)
Summary
Vulnerability in @orpc/server (CVE-2026-77360). Risk of unauthorized operations or information disclosure. Exploitable via Vary. Mitigation: upgrade to 1.14.8 or later.
Original description
The description as published by the source.
Summary
A flaw in the CORS plugin allowed the incoming request's Vary header to be reflected into the response, letting a client influence a header that should be controlled solely by the server.
Details
The CORS plugin previously copied the request's Vary header directly onto the response instead of treating Vary as a response-only header. Because Vary tells downstream caches and proxies how to key their cached responses, this allowed a client to inject arbitrary values into the response's Vary header, potentially distorting cache-key behavior in shared caches/CDNs sitting in front of an oRPC server and leading to inconsistent CORS enforcement for other clients.
Practical impact is limited to deployments where a shared cache or reverse proxy keys on the Vary header; the real-world effect depends on the caching layer's configuration.
Impact
May cause cache key pollution and inconsistent CORS enforcement in setups that rely on shared/edge caches keying on Vary. No direct confidentiality, integrity, or availability impact in default (non-cached) configurations.
Resolution
Update @orpc/server (and any other @orpc/* packages bundling the CORS plugin) to 1.14.8. The CORS plugin now derives Vary exclusively from the response, appending Origin and preserving existing values instead of reflecting request headers.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-77360 has been found in @orpc/server.
Attackers can target a specific entry point like Vary over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @orpc/server to 1.14.8 or later.
If unsure, ask your IT team or search "@orpc/server CVE-2026-77360" on the vendor's site.
CVE-2026-77360 (@orpc/server) — CWE-113
Attack surface: Vary / Origin
Patched: 1.14.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-113) exists in @orpc/server. Attackers reach the vulnerable code path via Vary.
Check the vendor advisory for the affected versions of @orpc/server. Attack surface: Vary / Origin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.14.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@orpc/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@orpc/server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@orpc/serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @orpc/server to 1.14.8ステージング環境で 1.14.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com