Quick answers
- Is CVE-2026-61013 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61013 being exploited in the wild.
- How severe is CVE-2026-61013?
- Medium severity, with a CVSS score of 6.6, published 21 July 2026.
- Which products and versions are affected?
- Oracle Time and Labor 12.2.3-12.2.15.
- Is there a fix for CVE-2026-61013?
- 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-61013 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-61013?
- Check whether you run Oracle Time and Labor 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 Internal Operations component of Oracle Time and Labor (versions 12.2.3 through 12.2.15). It is classified as difficult to exploit (High Attack Complexity) and requires High Privileges from the attacker. The attack vector is via the network over HTTP. A successful exploit results in a 'Scope Change' (S:C), meaning the attacker can impact components beyond the security scope of Oracle Time and Labor. Impact includes high confidentiality loss (unauthorized access to all data) and low integrity loss (unauthorized modification of some data). Users are advised to refer to the Oracle Critical Patch Update for July 2026 for remediation.
Affected products
- Oracle Time and Labor 12.2.3-12.2.15
Timeline
- 2026-07-21: disclosed: Initial disclosure by Oracle
- 2026-07-21: advisory: NVD record published