CVE-2026-77360: oRPC Vary Header Injection Vulnerability

MODERATE
Advisory Identifier: GHSA-j9v4-rhgr-4m5f
Share
CWE-113
Published
Advisory Summary

CVE-2026-77360 is a MODERATE vary header injection vulnerability (CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')) affecting oRPC libraries in the npm ecosystem. The issue involves vary header injection in cors plugin leading to potential cache/cors bypass. Remediation is available by upgrading affected packages to version 1.14.8.

CVE-2026-77360 at a Glance

CVE Identifier CVE-2026-77360
GHSA Identifier GHSA-j9v4-rhgr-4m5f
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Affected Product oRPC
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-77360

To remediate this vulnerability, upgrade all affected oRPC dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@orpc/server fixed: 1.14.8 
npm install @orpc/server@1.14.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @orpc/server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-77360, inspect your project dependencies using npm:

npm ls @orpc/server

Analyze the terminal output to locate any version of oRPC in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.14.8), your application is affected.

Note: The npm ls @orpc/server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'), where the product receives data from an http agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes cr and lf characters before the data is included in outgoing http headers. In oRPC, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2026-77360 Affected oRPC Versions

1 component(s)
Fixed Versions:
1.14.8
Product / Package Ecosystem Affected Versions Fixed Version
@orpc/server
npm/@orpc/server
npm
< 1.14.8
1.14.8

References

GitHub Advisory / Wiki ADVISORY
https://github.com/middleapi/orpc/security/advisories/GHSA-j9v4-rhgr-4m5f
NVD — CVE-2026-77360 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-77360
oRPC Source Repository REPOSITORY
https://github.com/middleapi/orpc/issues/1661
oRPC Source Repository REPOSITORY
https://github.com/middleapi/orpc/pull/1662
Security Fix Commit FIX COMMIT
https://github.com/middleapi/orpc/commit/daabded122a89d323357c4c401e879701864cb2f
oRPC Source Repository REPOSITORY
https://github.com/middleapi/orpc
oRPC Release RELEASE
https://github.com/middleapi/orpc/releases/tag/v1.14.8

Frequently Asked Questions

What is CVE-2026-77360?
CVE-2026-77360 is a security vulnerability in oRPC involving Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting').
Which oRPC versions are affected?
Affected versions include releases prior to 1.14.8 across affected packages: @orpc/server.
What version fixes CVE-2026-77360?
Upgrading to 1.14.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @orpc/server affected?
Yes, @orpc/server is affected in releases prior to 1.14.8. Upgrade your dependency to 1.14.8 or later.
What CWE is associated with CVE-2026-77360?
CVE-2026-77360 is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') (The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.).
How can I check npm dependencies for CVE-2026-77360?
Run the dependency tree command: 'npm ls @orpc/server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j9v4-rhgr-4m5f",
  "modified" : "2026-09-17T14:52:38Z",
  "published" : "2026-09-17T14:52:37Z",
  "aliases" : [ "CVE-2026-77360" ],
  "summary" : "oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass",
  "details" : "### Summary\nA 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.\n\n### Details\nThe 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.\n\nPractical 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.\n\n### Impact\nMay 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.\n\n### Resolution\nUpdate `@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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@orpc/server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.14.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.14.7"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/middleapi/orpc/security/advisories/GHSA-j9v4-rhgr-4m5f"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77360"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/middleapi/orpc/issues/1661"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/middleapi/orpc/pull/1662"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/middleapi/orpc/commit/daabded122a89d323357c4c401e879701864cb2f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/middleapi/orpc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/middleapi/orpc/releases/tag/v1.14.8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-113" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T14:52:37Z",
    "nvd_published_at" : "2026-09-16T19:17:38Z"
  }
}