Scalar TypeBox code injection in TypeCompiler
Affects @scalar/typebox 0.1.0 up to, but not including, 0.1.4 when an application passes crafted schema strings to TypeCompiler. Fixed in 0.1.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.1.4
- Who is exposed
- Specific setups only
Summary
@scalar/typebox has a code injection flaw in TypeCompiler. An attacker with local access and low privileges can run arbitrary JavaScript in the host Node.js process by supplying crafted schema strings. The flaw is triggered during Compile() and Check() when single-quote breakouts are injected into string formats, Kind names, property keys, or Literal values, and no user action is needed.
Written by a model
Original description
@scalar/typebox before 0.1.4 contains a code injection vulnerability in TypeCompiler that allows attackers to execute JavaScript by supplying crafted schema strings. Attackers can inject single-quote breakouts into string format, Kind names, property keys or Literal values to run arbitrary JavaScript in the host Node.js process during Compile() and Check().
Who should check
Teams running @scalar/typebox 0.1.x before 0.1.4 that use TypeCompiler Compile() or Check() on schema strings
“Affecting typebox >= 0.1.0, < 0.1.4”
What to do
Check whether your setup matches what the bug needs.
Affected @scalar/typebox versions 0.1.0 up to, but not including, 0.1.4 Application passes crafted schema strings to TypeCompiler Schemas are processed by TypeCompiler Compile() and Check()Upgrade to a fixed version: 0.1.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133309 (@scalar/typebox before 0.1.4 Code Injection via TypeCompiler Schema Strings), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133309 (entry last updated 2026-11-19):
Affected:
- npm package @scalar/typebox: from 0.1.0, fixed in 0.1.4
Fixed versions: 0.1.4.
Conditions (all must be true for the bug to be hit):
- Affected @scalar/typebox versions 0.1.0 up to, but not including, 0.1.4 (source: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings)
- Application passes crafted schema strings to TypeCompiler (source: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings)
- Schemas are processed by TypeCompiler Compile() and Check() (source: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-133309 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133309 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/scalar/typebox/pull/5
- https://github.com/scalar/typebox/commit/21d55f035a83868a3577be2142b9c9bbc125969b
- https://github.com/scalar/typebox/blob/v0.1.3/src/compiler/compiler.ts#L427
- https://github.com/sinclairzx81/sinclair-typebox/security/advisories/GHSA-976x-prgx-qv35
- https://www.npmjs.com/package/@scalar/typebox
- https://github.com/scalar/typebox
- https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133309
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133309"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach10/20Affects npm packages
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · sinclairzx81/sinclair-typebox · Advisory GHSA-976x-prgx-qv35 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133309 |
| Record | NVD · CVE-2026-133309 |
| Other links 6 | |
| Patch | GitHub · scalar/typebox · Pull request #5 |
| Patch | GitHub · scalar/typebox · Commit 21d55f03 |
| Repository | GitHub · scalar/typebox · src/compiler/compiler.ts · L427 |
| Repository | GitHub · scalar/typebox · Repository |
| Link | npmjs.com · package/@scalar/typebox |
| Link | vulncheck.com · advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings |
Questions about CVE-2026-133309
Is CVE-2026-133309 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Crafted schema strings passed to TypeCompiler can make the host Node.js process run arbitrary JavaScript. The code runs during Compile() and Check(), when the schemas are processed.
Source: vulncheck.com
Which versions are affected by CVE-2026-133309?
@scalar/typebox (npm): from 0.1.0 before 0.1.4.
Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are @scalar/typebox 0.1.0 up to, but not including, 0.1.4. The vulnerable setup is an application that passes schema strings to TypeCompiler. Check the installed version with npm ls @scalar/typebox, or in the version listed in package.json.
Source: vulncheck.com
How do I fix CVE-2026-133309?
Upgrade @scalar/typebox to 0.1.4, which is the fixed version.
Source: vulncheck.com
Related
- CVE-2026-130593Scalar scalar-ninja 0.1.0 before 0.3.3 XSS via Inline Configuration Script
- CVE-2026-130594Scalar scalar-ninja 0.1.0 before 0.3.3 XSS via ScalarConfig title
- CVE-2026-71499cf-manager: SSRF via URL-based Worker deployment allows arbitrary code execution in victim Cloudflare accounts
- CVE-2026-131253Remote Code Execution (RCE) through the App Wizard in Splunk SOAR
- CVE-2026-129048WordPress WP Photo Album Plus plugin <= 9.3.06.003 - Remote Code Execution (RCE) vulnerability
- CVE-2026-63411Jane: Instantiation RCE via parameter description -> raw PHPDoc */ breakout (jane-php/open-api-3)
No corrections so far. Something wrong on this page? Report an error.