Skip to content
Fencer Vulns
medium 4.9

CVE-2025-68463 json

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

published 2025-12-18 10 mo ago modified 2026-10-13 26 d ago also GHSA-x3vf-39hj-gxr4 , PYSEC-2026-1221 , EUVD-2025-204037

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

Bio.Entrez in Biopython through 186 allows doctype XXE.

Patch / fix

  • pypi biopython 1.87
  • python-biopython Debian 14 1.87+dfsg-1

debian advisories DEBIAN-CVE-2025-68463

  • python-biopython openSUSE Leap 16.0 1.85-bp160.2.1
  • python-biopython openSUSE Tumbleweed 1.87-1.1

opensuse advisories openSUSE-SU-2026:21169-1openSUSE-SU-2026:10537-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-68463 updated cvss 7.1

python-biopython: python-biopython: Information disclosure via XML External Entity (XXE) vulnerability in Bio.Entrez

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
10 mo ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi biopython
<=1.86
<1.87
1.87

Affected products

  • Biopython Biopython

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Vulns 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.