Skip to content
Fencer Intel
medium 6.4

CVE-2026-65973 json

Laradocs: Command injection via unescaped Node.js binary path in KaTeX SSR

published 4mo ago modified 12h ago also GHSA-h746-qpxh-ph7g , EUVD-2026-124034

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository PeteBishwhip/laradocs. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

Laradocs maintains version-controlled documentation inside a Laravel codebase. From version 0.4.0 to before version 1.0.0, Laradocs is vulnerable to local command injection in server-side KaTeX rendering via an unescaped Node.js binary path in a proc_open() command string. This issue has been patched in version 1.0.0.

Patch / fix

Is CVE-2026-65973 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • PeteBishwhip laradocs

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of PeteBishwhip/laradocs published their own advisory on GitHub. Reviewed sources take precedence over it.