How severe is CVE-2025-46599?

CVE-2025-46599 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-46599 being actively exploited?

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

How do I fix CVE-2025-46599?

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

Does CVE-2025-46599 have an EU (EUVD) identifier?

Yes. CVE-2025-46599 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-12401.

When was CVE-2025-46599 published?

CVE-2025-46599 was published on 2025-04-25 and last updated on 2026-06-17.

CVE-2025-46599

CVE-2025-46599 is a medium-severity vulnerability with a CVSS 3.x base score of 6.8. 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-1188.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (30th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-12401
Weakness: CWE-1188
Published: 2025-04-25
Last modified: 2026-06-17

Description

CNCF K3s 1.32 before 1.32.4-rc1+k3s1 has a Kubernetes kubelet configuration change with the unintended consequence that, in some situations, ReadOnlyPort is set to 10255. For example, the default behavior of a K3s online installation might allow unauthenticated access to this port, exposing credentials.

Frequently asked questions

What is CVE-2025-46599?: CNCF K3s 1.32 before 1.32.4-rc1+k3s1 has a Kubernetes kubelet configuration change with the unintended consequence that, in some situations, ReadOnlyPort is set to 10255. For example, the default behavior of a K3s online installation might allow unauthenticated access to this port, exposing credentials.
How severe is CVE-2025-46599?: CVE-2025-46599 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-46599 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-46599?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-46599 have an EU (EUVD) identifier?: Yes. CVE-2025-46599 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-12401.
When was CVE-2025-46599 published?: CVE-2025-46599 was published on 2025-04-25 and last updated on 2026-06-17.

References

Other CWE-1188 (Insecure Default Initialization of Resource) vulnerabilities

CVE-2026-31957 — Critical (CVSS 10.0): Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. From 3.0.0 to before 3.1.0, if…
CVE-2025-41672 — Critical (CVSS 10.0): A remote unauthenticated attacker may use default certificates to generate JWT Tokens and gain full access to the tool…
CVE-2024-0001 — Critical (CVSS 10.0): A condition exists in FlashArray Purity whereby a local account intended for initial array configuration remains active…
CVE-2024-2912 — Critical (CVSS 10.0): An insecure deserialization vulnerability exists in the BentoML framework, allowing remote code execution (RCE) by…
CVE-2021-34795 — Critical (CVSS 10.0): Multiple vulnerabilities in the web-based management interface of the Cisco Catalyst Passive Optical Network (PON)…
CVE-2017-7964 — Critical (CVSS 10.0): Zyxel WRE6505 devices have a default TELNET password of 1234 for the root and admin accounts, which makes it easier for…

Browse all CWE-1188 (Insecure Default Initialization of Resource) vulnerabilities →