Quick answers
- Is CVE-2026-60407 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60407 being exploited in the wild.
- How severe is CVE-2026-60407?
- Medium severity, with a CVSS score of 5.6, 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-60407?
- 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-60407 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-60407?
- 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 a confidentiality-impacting flaw that requires the attacker to have local logon access to the infrastructure where the database is executing. The attack complexity is high, suggesting specific timing or environmental conditions are necessary for exploitation. If successful, the attacker can achieve a scope change, potentially impacting products beyond the database itself and gaining unauthorized access to all accessible data. The vulnerability was disclosed as part of the Oracle July 2026 Critical Patch Update.
Affected products
- Oracle TimesTen In-Memory Database 26.1.1.1.0
Timeline
- 2026-07-21: disclosed: Initial disclosure by Oracle
- 2026-07-21: advisory: NVD entry published