How severe is CVE-2026-3446?

CVE-2026-3446 has a CVSS 4.0 base score of 6.0, rated medium severity.

Is CVE-2026-3446 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-3446?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-3446 have an EU (EUVD) identifier?

Yes. CVE-2026-3446 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-21545.

When was CVE-2026-3446 published?

CVE-2026-3446 was published on 2026-04-10 and last updated on 2026-06-17.

CVE-2026-3446

CVE-2026-3446 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: Medium (CVSS 4.0 base score 6.0)
EPSS exploit prediction: 0% (9th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-21545
Weakness: CWE-345
Published: 2026-04-10
Last modified: 2026-06-17

Description

When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data.

Frequently asked questions

What is CVE-2026-3446?: When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data.
How severe is CVE-2026-3446?: CVE-2026-3446 has a CVSS 4.0 base score of 6.0, rated medium severity.
Is CVE-2026-3446 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-3446?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-3446 have an EU (EUVD) identifier?: Yes. CVE-2026-3446 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-21545.
When was CVE-2026-3446 published?: CVE-2026-3446 was published on 2026-04-10 and last updated on 2026-06-17.

References

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-50214 — Critical (CVSS 9.8): The /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing…
CVE-2025-15385 — Critical (CVSS 9.8): Insufficient Verification of Data Authenticity vulnerability in TECNO Mobile com.Afmobi.Boomplayer allows…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →