Microsoft · base64.b64decode() always accepts "+/" characters, despite setting altchars
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium · fixed in 3.15.0a2 : update Microsoft when convenient.
Data as of 28 Oct 2026, 08:59 UTC
- Patch
- Available – fixed in 3.15.0a2, 3.14.1, 3.13.10
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade CPython to 3.15.0a2, 3.14.1 or 3.13.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
PyPIcpythonpkg:pypi/cpythonOther threats | Affected
| Fixed in– |
GitHubCPythonpkg:github/CPythonOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The vulnerability CVE-2025-12781 concerns the base64.b64decode() function in Microsoft software version 3.0, which always accepts the standard "+/" characters for decoding regardless of the altchars parameter setting. This behavior may lead to unexpected decoding results when alternative characters are intended to be used.