Vulnerabilities in pkg:npm/@typespec/openapi3
PACKAGEGHSA-2q42-4q24-7rgv is a HIGH (CVSS 7.1) openapi3 version value escapes `emitteroutputdir` vulnerability (CWE-73: External Control of File Name or Path) affecting @typespec/openapi3 libraries in the npm ecosystem. The issue involves openapi3 version value escapes `emitteroutputdir` and overwrites yaml/json outside the output tree. Remediation is available in the latest vendor maintenance releases.
pkg:npm/@typespec/openapi3
Vulnerability advisories affecting package pkg:npm/@typespec/openapi3. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-2q42-4q24-7rgv | - | HIGH | OpenAPI3 version value escapes `emitterOutputDir` and overwrites YAML/JSON outside the output tree |
GHSA-2q42-4q24-7rgv at a Glance
Security Impact
CVSS: 7.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H).
How to Fix GHSA-2q42-4q24-7rgv
To remediate this vulnerability, upgrade all affected @typespec/openapi3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @typespec/openapi3@Latest secure release
npm install @typespec/compiler@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @typespec/openapi3
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-2q42-4q24-7rgv, inspect your project dependencies using npm:
npm ls @typespec/openapi3
Analyze the terminal output to locate any version of @typespec/openapi3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The npm ls @typespec/openapi3 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-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In @typespec/openapi3, 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
GHSA-2q42-4q24-7rgv Affected @typespec/openapi3 Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@typespec/openapi3
|
npm |
≤ 1.15.0
|
|
|
@typespec/compiler
|
npm |
≤ 1.15.0
|
|
References
Frequently Asked Questions
What is GHSA-2q42-4q24-7rgv?
Which @typespec/openapi3 versions are affected?
What version fixes GHSA-2q42-4q24-7rgv?
Is @typespec/openapi3 affected?
Is @typespec/compiler affected?
What is the CVSS score of GHSA-2q42-4q24-7rgv?
What CWE is associated with GHSA-2q42-4q24-7rgv?
How can I check npm dependencies for GHSA-2q42-4q24-7rgv?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2q42-4q24-7rgv",
"modified" : "2026-09-08T21:31:09Z",
"published" : "2026-09-08T21:31:09Z",
"aliases" : [ ],
"summary" : "OpenAPI3 version value escapes `emitterOutputDir` and overwrites YAML/JSON outside the output tree",
"details" : "### Summary\n\nThe `@typespec/openapi3` emitter retains the value of a `@versioned` enum member and interpolates it into the output filename as `{version}` without sanitizing path separators or traversal components. The completed path reaches the compiler's `emitFile()`, which creates the parent directory and writes the file without verifying containment under `emitterOutputDir`.\n\nA crafted declarative `.tsp` input can therefore create or overwrite an OpenAPI-formatted `.yaml` or `.json` file outside the configured output tree, subject to the compiler process's filesystem permissions. No executable TypeSpec extension or attacker-controlled JavaScript is required.\n\n### Affected version\n\nConfirmed on:\n\n- `@typespec/compiler` `1.15.0`\n- `@typespec/openapi3` `1.15.0`\n- `@typespec/http` `1.15.0`\n- `@typespec/versioning` `0.85.0`\n- release tag commit `f30cd352f93997e04c75d48c7ace6947a1d5d07a`\n\nThe critical `openapi.ts` and `emitter-utils.ts` blobs are unchanged on main commit `365ec52b50b82cd9e1e037de4c6fcd5de7e32e90` as checked on 2026-08-19. No patched version was identified.\n\n### Root cause\n\nThe value originates at `packages/openapi3/src/openapi.ts:592-608`:\n\n```ts\nserviceRecord.versions.push({\n service,\n version: snapshot.version!.value,\n document: document[0],\n diagnostics: document[1],\n});\n```\n\nIt is interpolated without path validation at `openapi.ts:629-641`:\n\n```ts\nreturn interpolatePath(options.outputFile, {\n \"openapi-version\": specVersion,\n \"service-name-if-multiple\": multipleService ? getNamespaceFullName(service.type) : undefined,\n \"service-name\": getNamespaceFullName(service.type),\n \"file-type\": fileType,\n version,\n});\n```\n\nThe path reaches `emitFile()` at `openapi.ts:392-401`. The sink at `packages/compiler/src/core/emitter-utils.ts:29-39` performs no output-root containment check:\n\n```ts\nconst outputFolder = getDirectoryPath(options.path);\nawait program.host.mkdirp(outputFolder);\nreturn await program.host.writeFile(options.path, content);\n```\n\n`resolvePath()` joins the template to `emitterOutputDir` before `{version}` is interpolated, so it does not see the attacker-controlled `..` components.\n\n### Proof of concept\n\nThe relevant input in `poc/main.tsp` is:\n\n```tsp\n@versioned(Versions) namespace Svc;\nenum Versions { v1: \"../../../../../../../../../../tmp/TYPESPEC_PWNED/pwn\" }\n```\n\nRun from PowerShell:\n\n```powershell\ncd poc\n.\\run-revalidation.ps1\n```\n\nThe supplied Docker runner uses a digest-pinned Node base, a committed npm integrity lock, disabled runtime networking, a benign control, a 90-second timeout, and cleanup enforcement.\n\nObserved in the preserved identity-locked replay (`1/1` attack and `1/1` negative control):\n\n```text\nnegative_before=02dc7d056c2f773e56e2c1849947888b039f127ddd630c0bd76a5d7a9ca29cbd\nnegative_after=02dc7d056c2f773e56e2c1849947888b039f127ddd630c0bd76a5d7a9ca29cbd\nattack_before=7a8067bc04e42a025de90fd7aff9be4df59f005d192f2116eecfb107d7bffd78\nattack_after=2992b399c1573c9bd2130794f8554c4026bf425861f74e78b5d89ae0324b5e38\noutside_file_head=openapi: 3.0.0\ninside_attack_files=\n```\n\nThe benign version preserved the outside canary. The crafted version replaced it with emitted OpenAPI content, and no attack output file remained under `tsp-output`.\n\n### Impact and constraints\n\nProven impact is out-of-directory YAML/JSON creation or overwrite. The attacker can influence the traversal, final basename, and many strings in the OpenAPI-structured content. The extension is constrained to the selected emitter format, content is not arbitrary bytes, and the target must be writable.\n\nThis report demonstrates file corruption. Denial of service is a potential impact when a writable critical file is targeted. It does not claim file disclosure, arbitrary-byte write, deployment takeover, or code execution by a downstream consumer.\n\n### Suggested remediation\n\nAfter every filename token has been interpolated, resolve the completed destination against `emitterOutputDir` and reject any non-descendant using path-component-aware comparison. Reject or slugify absolute paths, path separators, and traversal components in spec-derived filename tokens. Add regression cases for POSIX and Windows separators, absolute values, sibling-prefix paths, and benign semantic versions.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@typespec/openapi3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.15.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@typespec/compiler"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.15.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/microsoft/typespec/security/advisories/GHSA-2q42-4q24-7rgv"
}, {
"type" : "WEB",
"url" : "https://github.com/microsoft/typespec/pull/11777"
}, {
"type" : "WEB",
"url" : "https://github.com/microsoft/typespec/commit/e0f67bdf3c5a0875dfa98b475648af37caac71a6"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/microsoft/typespec"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22", "CWE-73" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-08T21:31:09Z",
"nvd_published_at" : null
}
}