Skip to content

← Actionable
Unratedamended

HTML Injection in marky-markdown

GHSA-pxmp-fwjc-4x7q

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm marky-markdown

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

All versions of marky-markdown are vulnerable to HTML Injection due to a validation bypass. The package only allows iframes where the source is youtube.com but it is possible to bypass the validation with sources where youtube.com is the sub-domain, such as youtube.com.evil.co. This Recommendation This package is no longer maintained. Please upgrade to @npmcorp/marky-markdown

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-pxmp-fwjc-4x7q

  2. Revision 1 · created ·

    Published from osv record GHSA-pxmp-fwjc-4x7q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pxmp-fwjc-4x7q

Advisory: HTML Injection in marky-markdown
IDs: GHSA-pxmp-fwjc-4x7q
Record: https://patchnext.com/advisories/ghsa-pxmp-fwjc-4x7q (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm marky-markdown: affected every version

## Suggested inspection (read-only)
- `npm ls marky-markdown --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on marky-markdown.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pxmp-fwjc-4x7q (OSV record GHSA-pxmp-fwjc-4x7q lists affected ranges: npm marky-markdown >=0.0.0)
- Verified: https://github.com/advisories/GHSA-pxmp-fwjc-4x7q (GitHub-reviewed advisory GHSA-pxmp-fwjc-4x7q lists affected ranges: npm marky-markdown >=0.0.0)

Commands are suggestions: review each one before running it.

Loading voting…