Security Resilience

CVE-2026-9610

Ibm Datacap 9.1.7 … 9.1.9

Published
22 June 2026
Modified
26 June 2026
Patch / advisory
CVSS Score v3.1 2.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0026 18th percentile
Risk Priority 22 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-9610 is a low-severity Forced Browsing (CWE-425) vulnerability in Ibm Datacap. Its CVSS base score is 2.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
T1491.002 External Defacement Impact
An adversary may deface systems external to an organization in an attempt to deliver messaging, intimidate, or otherwise mislead an organization or users.
T1530 Data from Cloud Storage Collection
Adversaries may access data from cloud storage.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-36027Same product: Ibm Datacap
CVE-2024-39737Same product: Ibm Datacap
CVE-2026-8636Same product: Ibm Datacap
CVE-2024-39736Same product: Ibm Datacap
CVE-2024-39739Same product: Ibm Datacap
CVE-2024-39741Same product: Ibm Datacap
CVE-2024-39729Same product: Ibm Datacap
CVE-2025-36026Same product: Ibm Datacap
CVE-2026-8059Same product: Ibm Datacap
CVE-2024-39728Same product: Ibm Datacap

Affected Assets

ibm
datacap
9.1.7, 9.1.8, 9.1.9
ibm
datacap navigator
9.1.7, 9.1.8, 9.1.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.

AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.

AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.AA-05 full match
blocks

Directly requires policy-driven definition, enforcement, and review of authorizations on resources such as URLs.

PR.IR-01 mostly match
blocks

Protects environments from unauthorized logical access, which includes preventing direct requests to restricted paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

removes

A.8.3 mandates access controls on information in systems, applications and services (guidance items b, c, d), and when applied to a web application with CWE-425 flaws, requires authorization checks on all restricted URLs/scripts/files, removing the weakness.

finds

Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.

prevents

Secure coding practices reduce the likelihood of missing authorization checks, yet do not guarantee coverage.

finds

A.8.8's reach is DISCLOSURE — it sees vulnerabilities through published advisories, vendor CVE feeds, and scanning against known-flaw inventories. CWE-425 (forced browsing) does surface as CVEs (multiple examples in the CWE entry), so the disclosed minority is reachable, but the bulk of forced-browsing instances are first-party authorization flaws in custom web applications that never receive a CVE and are outside A.8.8's disclosure-based reach.

References