CVE-2026-58243
High (8.8) vulnerability enables system compromise; technical details blocked.
Is CVE-2026-58243 being exploited?
Not confirmed. CVE-2026-58243 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-58243?
CVE-2026-58243 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-2026-58243?
Not known from our data. No patch reference has been recorded for CVE-2026-58243, 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-2026-58243 affect?
CVE-2026-58243 affects Unknown (details blocked). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58243?
Inventory exposures, apply vendor patch immediately when released, restrict access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
High-severity flaw allowing remote code execution or unauthorized system takeover leading to data access, persistence, and full system compromise.
Immediate action required
- affectedSAP_BASIS 750
- affectedSAP_BASIS 751
- affectedSAP_BASIS 752
- affectedSAP_BASIS 753
- affectedSAP_BASIS 754
- affectedSAP_BASIS 755
- affectedSAP_BASIS 756
- affectedSAP_BASIS 757
- affectedSAP_BASIS 758
- affectedSAP_BASIS 816
- affectedSAP_BASIS 918
- affectedSAP_BASIS 920
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.