LiveActive security incident?Get immediate response
CVE Record

CVE-2021-3426: There's a flaw in Python 3's pydoc.

There's a flaw in Python 3's pydoc. A local or adjacent attacker who discovers or is able to convince another local or adjacent user to start a pydoc server could access the server and use it to disclose sensitive information belonging to the other user that they would not normally be able to access. The highest risk of this flaw is to data confidentiality. This flaw affects Python versions before 3.8.9, Python versions before 3.9.3 and Python versions before 3.10.0a7.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-3426 is a Python pydoc information-disclosure flaw. If a vulnerable pydoc server is started, a local or nearby network attacker may access it and read sensitive information belonging to another user. The issue is not described as remotely exploitable from the internet by default.

Executive priority

Treat this as a moderate confidentiality issue. Prioritize shared systems, developer environments, and internal platforms where untrusted local or adjacent users may coexist. It is lower urgency than internet-facing remote execution flaws, but should be remediated through normal patch management.

Technical view

The flaw affects Python 3 pydoc before Python 3.8.9, 3.9.3, and 3.10.0a7. It is categorized as CWE-200 with CVSS 3.1 score 5.7, requiring adjacent access and low privileges, with high confidentiality impact and no integrity or availability impact.

Likely exposure

Exposure is most likely on developer workstations, shared servers, lab systems, or internal hosts where vulnerable Python 3 versions remain installed and pydoc can be started or reached by other local or adjacent users.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The described condition requires a pydoc server to be started, either by the victim or through persuasion, and then accessed by a local or adjacent attacker.

Researcher notes

Evidence supports an information disclosure issue in Python pydoc under local or adjacent access conditions. The bundle does not provide exploit details, affected downstream product breadth, or active exploitation evidence. Validate exposure by version, runtime packaging, and whether pydoc is reachable beyond the intended user.

Mitigation direction

  • Upgrade Python to 3.8.9, 3.9.3, 3.10.0a7, or later fixed builds.
  • Apply relevant distribution security updates from Debian, Fedora, Gentoo, or vendor channels.
  • Avoid running pydoc servers on shared or adjacent-accessible systems unless necessary.
  • Restrict pydoc access to trusted local users and trusted network paths.
  • Check vendor guidance for appliances or bundled Python runtimes.

Validation and detection

  • Inventory Python 3 versions across workstations, servers, and packaged appliances.
  • Confirm vulnerable versions before 3.8.9, 3.9.3, or 3.10.0a7 are remediated.
  • Review systems for running pydoc services or exposed documentation servers.
  • Validate distribution package versions against applicable security advisories.
  • Document exceptions where vendor-fixed bundled Python cannot be upgraded directly.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-3426 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
16Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.7Medium
CVSS 3.1 vector shape for CVE-2021-3426Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/apythonpython 3.8.9, python 3.9.3, python 3.10.0a7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.