Skip to main content
CVE-2025-12781VulnerabilityPublished Updated

Microsoft · base64.b64decode() always accepts "+/" characters, despite setting altchars

Affects MicrosoftSource GCVE Database

0
Authoritative record:CVE-2025-12781· Medium 6.3

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

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Python Software FoundationCPythonAffected
  • >=3.15.0a1 <3.15.0a2
Fixed in
  • 3.15.0a2
Python Software FoundationCPythonAffected
  • >=3.14.0 <3.14.1
Fixed in
  • 3.14.1
Python Software FoundationCPythonAffected
  • <3.13.10
Fixed in
  • 3.13.10
PyPIcpythonpkg:pypi/cpythonOther threatsAffected
  • =0
  • =3.14.0
  • =3.15.0
Fixed in–
GitHubCPythonpkg:github/CPythonOther threatsAffected
  • <3.13.10
  • >=3.14.0 <3.14.1
  • >=3.15.0a1 <3.15.0a2
Fixed in
  • 3.13.10
  • 3.14.1
  • 3.15.0a2

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.

References

Community reviews

Loading reviews…