Quick answers
- Is CVE-2026-60405 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60405 being exploited in the wild.
- How severe is CVE-2026-60405?
- Low severity, with a CVSS score of 3.8, 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-60405?
- 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-60405 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-60405?
- 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
This vulnerability affects the Kubernetes Operator component of Oracle TimesTen In-Memory Database version 26.1.1.1.0. It is classified as an information disclosure flaw that is easily exploitable by an attacker with local logon access to the infrastructure where the database executes. The exploit results in a scope change (S:C), meaning the impact can extend beyond the immediate database component to other products in the environment. Successful exploitation allows unauthorized read access to a subset of accessible data. Oracle addressed this in the July 2026 Critical Patch Update.
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