EUVD-2026-80991Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AC:H because impact requires a specific Vary-keyed shared-cache topology; S:C and I:L because harm is cache-key pollution affecting other clients, with no direct confidentiality or availability loss.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
4DescriptionCVE.org
oRPC is an tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards. Prior to 1.14.8, the @orpc/server CORS plugin in packages/server/src/plugins/cors.ts copies a client's incoming Vary request header into the response instead of controlling Vary as a response-only header and using Origin for request-origin variation. In deployments behind a shared cache, CDN, or reverse proxy that keys responses using Vary, a client can inject arbitrary variation values, pollute cache keys, and cause inconsistent CORS enforcement for other clients. Default non-cached configurations have no established direct confidentiality, integrity, or availability impact. This issue is fixed in version 1.14.8.
AnalysisAI
Cache-key pollution in the @orpc/server CORS plugin (oRPC versions prior to 1.14.8) allows remote, unauthenticated clients to inject arbitrary Vary header values that are copied verbatim into HTTP responses, poisoning the cache keys used by shared caches, CDNs, or reverse proxies and producing inconsistent CORS enforcement for other clients. No authentication or user interaction is required (CVSS 4.0 vector shows PR:N/UI:N), but the impact is gated by deployment topology: per the vendor and independent assessment, default non-cached configurations have no established confidentiality, integrity, or availability impact, so single-instance or non-CDN deployments are effectively unaffected. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the oRPC @orpc/server CORS plugin (packages/server/src/plugins/cors.ts) in a version prior to 1.14.8, AND the API must be deployed behind a shared cache, CDN, or reverse proxy that keys/varies cached responses using the Vary header. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuinely low-to-moderate risk, cache-behavior integrity issue rather than a code-execution flaw despite the misleading 'Code Injection' tag. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade @orpc/server to version 1.14.8 or later - the vendor-released patch is 1.14.8 (release tag v1.14.8, commit daabded122a89d323357c4c401e879701864cb2f in PR #1662) - and verify after upgrading that responses always emit a normalized, server-controlled Vary: Origin and never echo a client-supplied Vary value. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-113 – HTTP Response Splitting
View allShare
External POC / Exploit Code
Leaving vuln.today