Skip to content
Applications

CVE-2026-10543

HIGH
High
EPSS 0.27%Patch availableAug 13, 2026

High-severity unspecified vulnerability (CVE-2026-10543) requiring investigation.

common questions

Is CVE-2026-10543 being exploited?

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

How severe is CVE-2026-10543?

CVE-2026-10543 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-10543?

Yes. A fix has been recorded for CVE-2026-10543. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-10543 affect?

CVE-2026-10543 affects Unknown/unspecified products, Check vendor advisories for specific affected versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-10543?

Monitor vendor advisories, prioritize testing and apply vendor patch 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/unspecified productsCheck vendor advisories for specific affected versions
impact

High-severity flaw that can enable remote code execution or privilege escalation depending on product, allowing unauthorized control or data access.

action required

Patch when possible

affected versions
IBM Db2
  • affected>= 11.5.0 and <= 11.5.9
  • affected>= 12.1.0 and <= 12.1.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