Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-68463 medium CVSS 4.9

XXE (XML External Entity) in biopython (CVE-2025-68463)

Summary

Vulnerability in biopython (CVE-2025-68463). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

Bio.Entrez in Biopython through 186 allows doctype XXE.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2025-68463 was discovered in biopython.
Severity is Medium (CVSS 4.9/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "biopython CVE-2025-68463".

CVE-2025-68463 (biopython). Severity: Medium / CVSSv3 4.9. Category: CWE-611.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2025-68463) in biopython. A serious software flaw has been identified.

📍 Affected scope

Target versions of biopython (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Medium (CVSS 4.9/10). Exploitation requires specific conditions but can cause real harm if successful.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-611)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    依存マニフェストで影響コンポーネントを特定する。

  2. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip biopython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
PyPI biopython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.86"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details