Skip to content

← Actionable
Unratedamended

SVG with embedded scripts can lead to cross-site scripting attacks in xml2rfc

GHSA-cf4q-4cqr-7g7w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (xml2rfc 3.12.4), redeploy, then verify what is actually installed.

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

  • PyPI xml2rfc

    Affected
    < 3.12.4
    Fixed in
    3.12.4

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.

xml2rfc allows script elements in SVG sources. In HTML output having these script elements can lead to XSS attacks. Sample XML snippet: Impact This vulnerability impacts website that publish HTML drafts and RFCs. Patches This has been fixed in version 3.12.4. Workarounds If SVG source is self-contained within the XML, scraping script elements from SVG files. References https://developer.mozilla.org/en-US/docs/Web/SVG/Element/script For more information If you have any questions or comments about this advisory: Open an issue in xml2rfc Email us at operational-vulnerability@ietf.org Infrastructure and Services Vulnerability Disclosure

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

    Amended from ghsa record GHSA-cf4q-4cqr-7g7w

  2. Revision 1 · created ·

    Published from osv record GHSA-cf4q-4cqr-7g7w

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-cf4q-4cqr-7g7w

Advisory: SVG with embedded scripts can lead to cross-site scripting attacks in xml2rfc
IDs: GHSA-cf4q-4cqr-7g7w
Record: https://patchnext.com/advisories/ghsa-cf4q-4cqr-7g7w (revision 2, source checked 26 Oct 2026, 13:08 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 fix available; fixed versions by package: xml2rfc 3.12.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI xml2rfc: affected < 3.12.4; fixed in 3.12.4

## Suggested inspection (read-only)
- `python -m pip show xml2rfc`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on xml2rfc.
- 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-cf4q-4cqr-7g7w (OSV record GHSA-cf4q-4cqr-7g7w lists affected ranges: PyPI xml2rfc >=0 <3.12.4 (fixed))
- Verified: https://github.com/advisories/GHSA-cf4q-4cqr-7g7w (GitHub-reviewed advisory GHSA-cf4q-4cqr-7g7w lists affected ranges: PyPI xml2rfc >=0 <3.12.4)

Commands are suggestions: review each one before running it.

Loading voting…