Skip to main content
Menu
CVEs

CVE

Contentlayer Source Files code injection in Markdown frontmatter handling

Affects @contentlayer/source-files through 0.3.4 when it parses Markdown or MDX files whose frontmatter uses a js or javascript delimiter, in builds that process content files an attacker can control.

CVE-2026-129948

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Contentlayer @contentlayer/source-files through 0.3.4 is used to parse content. The attacker must be able to control content files that the build processes. The content file is a Markdown or MDX file whose frontmatter uses a js or javascript delimiter.

Published
Last modified
Reference
Last checked
32/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

The Contentlayer @contentlayer/source-files package has a code injection flaw that lets an attacker who controls content files run JavaScript during the build by starting a Markdown or MDX file with a ---js or ---javascript frontmatter delimiter, which can expose CI build secrets. An attacker can reach it over the network with low-privilege access and no user interaction.

Original description

Contentlayer @contentlayer/source-files through 0.3.4 contains a code injection vulnerability that allows attackers who control content files to execute JavaScript by abusing gray-matter's still-enabled JavaScript engine in parseMarkdown(). Attackers can start a Markdown or MDX file with a ---js or ---javascript frontmatter delimiter to run code during build, exposing CI build secrets.

Who should check

Teams building Contentlayer sites from Markdown or MDX content they do not fully control, including CI builders, using @contentlayer/source-files through 0.3.4.

“Contentlayer @contentlayer/source-files through 0.3.4”

vulncheck.com

cve.now Index

32Pcve.now Index 32 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects npm packages
  • Severity8.7/10CVSS 8.7
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 39 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Contentlayer @contentlayer/source-files through 0.3.4 is used to parse content. The attacker must be able to control content files that the build processes. The content file is a Markdown or MDX file whose frontmatter uses a js or javascript delimiter.
  • Workaround: Until a fix is available, limit the build to content files from trusted sources and remove js or javascript frontmatter delimiters from content files. Keep secrets out of CI builds that process untrusted content where possible.

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-129948 (Contentlayer @contentlayer/source-files through 0.3.4 Code Injection via JavaScript Frontmatter), 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-129948 (entry last updated 2026-11-16):
Affected:
- npm package @contentlayer/source-files: through 0.3.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Contentlayer @contentlayer/source-files through 0.3.4 is used to parse content. (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-source-files-through-0.3.4-code-injection-via-javascript-frontmatter)
- The attacker must be able to control content files that the build processes. (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-source-files-through-0.3.4-code-injection-via-javascript-frontmatter)
- The content file is a Markdown or MDX file whose frontmatter uses a js or javascript delimiter. (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-source-files-through-0.3.4-code-injection-via-javascript-frontmatter)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129948 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129948 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/contentlayerdev/contentlayer/issues/688
- https://github.com/contentlayerdev/contentlayer/blob/v0.3.4/packages/@contentlayer/source-files/src/fetchData/makeCacheItemFromFilePath.ts#L221-L228
- https://www.vulncheck.com/advisories/contentlayer-contentlayer-source-files-through-0.3.4-code-injection-via-javascript-frontmatter
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-129948
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-129948"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Report
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129948

Is CVE-2026-129948 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?

A crafted Markdown or MDX content file can run arbitrary JavaScript during the build, which can expose CI build secrets.Source: vulncheck.com

Which versions are affected by CVE-2026-129948?

@contentlayer/source-files (npm): through 0.3.4.Source: cve.now feed data

Am I affected, and how do I check?

Versions through 0.3.4 of @contentlayer/source-files are in the affected range. The exposure applies to content files that start with a ---js or ---javascript frontmatter delimiter and that the build processes. Check the installed version with npm ls @contentlayer/source-files and search content files for those delimiters.Source: vulncheck.com

How do I fix CVE-2026-129948?

The checked facts name no fixed version or vendor patch, so no upgrade target can be given from them. Check the vendor's advisory for a patched release before updating.Source: vulncheck.com

What if there's no patch?

Until a fix is available, limit the build to content files from trusted sources and remove js or javascript frontmatter delimiters from content files. Keep secrets out of CI builds that process untrusted content where possible.Source: vulncheck.com