Quick answers
- Is CVE-2026-60409 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60409 being exploited in the wild.
- How severe is CVE-2026-60409?
- Medium severity, with a CVSS score of 5.7, 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-60409?
- 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-60409 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-60409?
- 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 local exploit requiring high privileges (PR:H), meaning the attacker must already have significant access to the infrastructure where the database is running. The flaw is characterized by a 'scope change' (S:C), indicating that a successful exploit can impact components beyond the immediate database environment. Attackers can achieve unauthorized read, update, insert, or delete access to database data, as well as cause a partial denial of service (DoS). The vulnerability is easily exploitable once the prerequisite access is obtained.
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 record published