Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

xml2rfc has file inclusion irregularities

GHSA-432c-wxpg-m4q3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (xml2rfc 3.27.0), 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.

Add to your agent

Affected packages

  • PyPI xml2rfc

    Affected
    >= 3.12.0, < 3.27.0
    Fixed in
    3.27.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Version 3.12.0 changed xml2rfc so that it would not access local files without the presence of its new --allow-local-file-access flag. This prevented XML External Entity (XXE) injection attacks with xinclude and XML entity references. It was discovered that xml2rfc does not respect --allow-local-file-access when a local file is specified as src in artwork or sourcecode elements. Furthermore, XML entity references can include any file inside the source dir and below without using the --allow-local-file-access flag. The xml2rfc <= 3.26.0 behaviour: | | xinclude | XML entity reference | artwork src= | sourcecode src= | |---|---|---|---|---| | without --allow-local-file-access flag | No filesystem access | Any file in xml2rfc templates dir and below, any file in source directory and below | Access source directory and below | Access source directory and below | | with --allow-local-file-access flag | Access any file on filesystem[^1] | Access any file on filesystem[^1] | Access source…

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

    Amended from ghsa record GHSA-432c-wxpg-m4q3

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-432c-wxpg-m4q3

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-432c-wxpg-m4q3

Advisory: xml2rfc has file inclusion irregularities
IDs: GHSA-432c-wxpg-m4q3
Record: https://patchnext.com/advisories/ghsa-432c-wxpg-m4q3 (revision 3, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: xml2rfc 3.27.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI xml2rfc: affected >= 3.12.0, < 3.27.0; fixed in 3.27.0

## 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-432c-wxpg-m4q3 (OSV record GHSA-432c-wxpg-m4q3 lists affected ranges: PyPI xml2rfc >=3.12.0 <3.27.0 (fixed))
- Verified: https://github.com/advisories/GHSA-432c-wxpg-m4q3 (GitHub-reviewed advisory GHSA-432c-wxpg-m4q3 lists affected ranges: PyPI xml2rfc >=3.12.0 <3.27.0)

Commands are suggestions: review each one before running it.

Loading voting…