<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T06:33:31.772388+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-262992</id>
    <title>EUVD-2026-262992</title>
    <updated>2026-10-09T06:33:31.828829+00:00</updated>
    <content>EUVD-2026-262992</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-262992"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-66456</id>
    <title>fkie_cve-2025-66456</title>
    <updated>2026-10-09T06:33:31.828871+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Elysia is a Typescript framework for request validation, type inference, OpenAPI documentation and client-server communication. Versions 1.4.0 through 1.4.16 contain a prototype pollution vulnerability in `mergeDeep` after merging results of two standard schema validations with the same key. Due to the ordering of merging, there must be an any type that is set as a standalone guard, to allow for the `__proto__ prop` to be merged. When combined with GHSA-8vch-m3f4-q8jf this allows for a full RCE by an attacker. This issue is fixed in version 1.4.17. To workaround, remove the `__proto__ key` from body.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-66456"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hxj9-33pp-j2cc</id>
    <title>GHSA-hxj9-33pp-j2cc — Elysia vulnerable to prototype pollution with multiple standalone schema validation</title>
    <updated>2026-10-09T06:33:31.828908+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: elysia</p>
<p>Prototype pollution vulnerability in `mergeDeep` after merging results of two standard schema validations with the same key. Due to the ordering of merging, there must be an `any` type that is set as a `standalone` guard, to allow for the `__proto__` prop to be merged.</p>
<p>When combined with GHSA-8vch-m3f4-q8jf this allows for a full RCE by an attacker.</p>
<p>### Impact
Routes with more than 2 standalone schema validation, eg. zod</p>
<p>Example vulnerable code:
```typescript
import { Elysia } from "elysia"
import * as z from "zod"</p>
<p>const app = new Elysia()
	.guard({
		schema: "standalone",
		body: z.object({
			data: z.any()
		})
	})
	.post("/", ({ body }) =&gt; ({ body, win: {}.foo }), {
		body: z.object({
			data: z.object({
				messageId: z.string("pollute-me"),
			})
		})
	})
```</p>
<p>### Patches
Patched by 1.4.17 (https://github.com/elysiajs/elysia/pull/1564)</p>
<p>Reference commit:
- https://github.com/elysiajs/elysia/pull/1564/commits/26935bf76ebc43b4a43d48b173fc853de43bb51e
- https://github.com/elysiajs/elysia/pull/1564/commits/3af978663e437dccc6c1a2a3aff4b74e1574849e</p>
<p>### Workarounds
Remove `__proto__` key from body</p>
<p>Example plugin for removing `__proto__` from body</p>
<p>```typescript
new Elysia()
	.onTransform(({ body, headers }) =&gt; {
		if (headers['content-type'] === 'application/json')
			return JSON.parse(JSON.stringify(body), (k, v) =&gt; {
				if (k === '__proto__') return</p>
<p>return v
			})
	})
```</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hxj9-33pp-j2cc"/>
  </entry>
</feed>
