CVE-2026-9610

CVE-2026-9610 is a low-severity vulnerability in Ibm Datacap with a CVSS 3.x base score of 2.3. 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-425.

Key facts

Description

IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.1.8, and 9.1.9 exposes resources or functionality that isn't linked in the UI but is accessible by directly requesting the URL, bypassing intended access controls.

Frequently asked questions

What is CVE-2026-9610?
IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.1.8, and 9.1.9 exposes resources or functionality that isn't linked in the UI but is accessible by directly requesting the URL, bypassing intended access controls.
How severe is CVE-2026-9610?
CVE-2026-9610 has a CVSS 3.x base score of 2.3, rated low severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-9610 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-9610?
CVE-2026-9610 primarily affects Ibm Datacap. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-9610?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-9610 have an EU (EUVD) identifier?
Yes. CVE-2026-9610 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38287.
When was CVE-2026-9610 published?
CVE-2026-9610 was published on 2026-06-22 and last updated on 2026-06-26.

References

Affected products (6)

More vulnerabilities in Ibm Datacap

All CVEs affecting Ibm Datacap →

Other CWE-425 vulnerabilities

Browse all CWE-425 vulnerabilities →