Quick answers
- Is CVE-2026-60401 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60401 being exploited in the wild.
- How severe is CVE-2026-60401?
- Medium severity, with a CVSS score of 6.5, published 21 July 2026.
- Which products and versions are affected?
- Oracle TimesTen In-Memory Database 26.1.1.1.0.
- Is there a fix for CVE-2026-60401?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-60401 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-60401?
- Check whether you run Oracle TimesTen In-Memory Database at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in the Kubernetes Operator component of Oracle TimesTen In-Memory Database (version 26.1.1.1.0) allows for unauthorized data access. The flaw is categorized by a CVSS 3.1 score of 6.5, specifically noting a 'Scope Change' (S:C), which implies that an exploit can impact components beyond the database itself. An attacker with low-privileged local access to the infrastructure where the database executes can exploit this vulnerability to achieve high confidentiality impact (C:H). No user interaction is required for exploitation. Users are advised to refer to the Oracle July 2026 Critical Patch Update for remediation details.
Affected products
- Oracle TimesTen In-Memory Database 26.1.1.1.0
Timeline
- 2026-07-21: disclosed
- 2026-07-21: advisory: Oracle July 2026 Critical Patch Update published.