CVE-2025-30241
High-severity vulnerability (CVE-2025-30241) with potential remote compromise risk.
Is CVE-2025-30241 being exploited?
Not confirmed. CVE-2025-30241 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2025-30241?
CVE-2025-30241 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-30241?
Not known from our data. No patch reference has been recorded for CVE-2025-30241, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-30241 affect?
CVE-2025-30241 affects Unknown/Details blocked - vendor/product not disclosed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-30241?
Monitor vendor advisories, apply vendor patch ASAP, restrict access and increase logging/IDS.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Potential remote code execution enabling attackers to run arbitrary code and gain full system control or data access.
Immediate action required
- affected< 0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
- affected< 0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
- affected< 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
- affected< 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
- affected< 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
- affected< 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
- affected< 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
- affected< 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
- affected< 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
- affected< 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
- affected< 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
- affected< 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
- affected< 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
- affected< 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
- affected< 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
- affected< 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
- affected< 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
- affected< 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
- affected< 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
- affected< 0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n
- affected< 800.0.16
- affected< 0.16.0 3.0.0 v6066.0 Build 250423 Rel.43799n
- affected< 0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n
- affected< 0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.