Skip to content
Applications

CVE-2026-44758

CRITICAL
Critical
EPSS 0.67%Aug 11, 2026

Critical CVE-2026-44758: details blocked; treat as high-risk RCE/complete compromise.

common questions

Is CVE-2026-44758 being exploited?

Not confirmed. CVE-2026-44758 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.67% probability of exploitation in the next 30 days.

How severe is CVE-2026-44758?

CVE-2026-44758 is rated Critical. 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-44758?

Not known from our data. No patch reference has been recorded for CVE-2026-44758, 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-44758 affect?

CVE-2026-44758 affects Unknown - affected products not disclosed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-44758?

Isolate exposed systems, block access, monitor vendor/NVD and apply patches immediately when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Unknown - affected products not disclosed
impact

Likely enables remote code execution and full system compromise via remote exploit.

action required

Immediate action required

affected versions
SAP_SE SAP Manufacturing Integration and Intelligence
  • affectedXMII 15.4
  • affected15.5

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free