<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 10:00:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-370005</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-370005</link>
      <description>EUVD-2026-370005</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-370005</guid>
    </item>
    <item>
      <title>fkie_cve-2026-77360</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77360</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-77360</guid>
    </item>
    <item>
      <title>GHSA-j9v4-rhgr-4m5f — oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j9v4-rhgr-4m5f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @orpc/server&lt;/p&gt;
&lt;p&gt;### Summary
A flaw in the CORS plugin allowed the incoming request&amp;#39;s `Vary` header to be reflected into the response, letting a client influence a header that should be controlled solely by the server.&lt;/p&gt;
&lt;p&gt;### Details
The CORS plugin previously copied the request&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s configuration.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @orpc/server&lt;/p&gt;
&lt;p&gt;### Summary
A flaw in the CORS plugin allowed the incoming request&amp;#39;s `Vary` header to be reflected into the response, letting a client influence a header that should be controlled solely by the server.&lt;/p&gt;
&lt;p&gt;### Details
The CORS plugin previously copied the request&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s configuration.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j9v4-rhgr-4m5f</guid>
    </item>
  </channel>
</rss>
