<?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>Thu, 08 Oct 2026 04:56:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266500</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266500</link>
      <description>EUVD-2026-266500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266500</guid>
    </item>
    <item>
      <title>fkie_cve-2026-24132</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24132</link>
      <description>&lt;p&gt;Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions 
7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. The vulnerability is similar in impact to the previously reported enum x-enumDescriptions (GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core. The issue has been fixed in versions 7.20.0 and 8.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions 
7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. The vulnerability is similar in impact to the previously reported enum x-enumDescriptions (GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core. The issue has been fixed in versions 7.20.0 and 8.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-24132</guid>
    </item>
    <item>
      <title>GHSA-f456-rf33-4626 — Orval Mock Generation Code Injection via const</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f456-rf33-4626</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @orval/mock&lt;/p&gt;
&lt;p&gt;I am reporting a code injection vulnerability in Orval’s mock generation pipeline affecting @orval/mock in both the 7.x and 8.x series. This issue is related in impact to the previously reported enum x-enumDescriptions (https://github.com/advisories/GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core.&lt;/p&gt;
&lt;p&gt;The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. I have confirmed that this occurs on orval@7.19.0 and orval@8.0.2 with mock: true, and that the generated mocks contain executable payloads such as require(&amp;#39;child_process&amp;#39;).execSync(&amp;#39;id&amp;#39;) in the output TypeScript.&lt;/p&gt;
&lt;p&gt;```yaml
openapi: 3.1.0
info:
  title: Mock Const Injection PoC
  version: 1.0.0
paths:
  /test:
    get:
      operationId: getTests
      responses:
        &amp;#39;200&amp;#39;:
          description: OK
          content:
            application/json:
              schema:
                $ref: &amp;#39;#/components/schemas/Tests&amp;#39;
components:
  schemas:
    Tests:
      type: object
      properties:
        EvilString:
          type: string
          const: &amp;#34;&amp;#39;); requ…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @orval/mock&lt;/p&gt;
&lt;p&gt;I am reporting a code injection vulnerability in Orval’s mock generation pipeline affecting @orval/mock in both the 7.x and 8.x series. This issue is related in impact to the previously reported enum x-enumDescriptions (https://github.com/advisories/GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core.&lt;/p&gt;
&lt;p&gt;The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. I have confirmed that this occurs on orval@7.19.0 and orval@8.0.2 with mock: true, and that the generated mocks contain executable payloads such as require(&amp;#39;child_process&amp;#39;).execSync(&amp;#39;id&amp;#39;) in the output TypeScript.&lt;/p&gt;
&lt;p&gt;```yaml
openapi: 3.1.0
info:
  title: Mock Const Injection PoC
  version: 1.0.0
paths:
  /test:
    get:
      operationId: getTests
      responses:
        &amp;#39;200&amp;#39;:
          description: OK
          content:
            application/json:
              schema:
                $ref: &amp;#39;#/components/schemas/Tests&amp;#39;
components:
  schemas:
    Tests:
      type: object
      properties:
        EvilString:
          type: string
          const: &amp;#34;&amp;#39;); requ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f456-rf33-4626</guid>
    </item>
  </channel>
</rss>
