Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.9amended

Biopython is vulnerable to doctype XML external entity (XXE) injection through Bio.Entrez

CVE-2025-68463GHSA-x3vf-39hj-gxr4

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.

Add to your agent

Affected packages

  • PyPI biopython

    Affected
    <= 1.86
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.9 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:L
EPSS
  • CVE-2025-68463: 0.32% estimated exploitation activity in the next 30 days; percentile 24.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Bio.Entrez in Biopython through 1.86 allows doctype XXE.

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

    Amended from ghsa record GHSA-x3vf-39hj-gxr4

  2. Revision 1 · created ·

    Published from osv record GHSA-x3vf-39hj-gxr4

Agent brief

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

# Patch Next advisory brief: CVE-2025-68463

Advisory: Biopython is vulnerable to doctype XML external entity (XXE) injection through Bio.Entrez
IDs: CVE-2025-68463, GHSA-x3vf-39hj-gxr4
Record: https://patchnext.com/advisories/cve-2025-68463 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
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
- PyPI biopython: affected <= 1.86

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

## 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 biopython.
- 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-x3vf-39hj-gxr4 (OSV record GHSA-x3vf-39hj-gxr4 lists affected ranges: PyPI biopython >=0 <=1.86)
- Verified: https://github.com/advisories/GHSA-x3vf-39hj-gxr4 (GitHub-reviewed advisory GHSA-x3vf-39hj-gxr4 lists affected ranges: PyPI biopython >=0 <=1.86)

Commands are suggestions: review each one before running it.

Loading voting…