Quick answers
- Is CVE-2026-61015 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61015 being exploited in the wild.
- How severe is CVE-2026-61015?
- Low severity, with a CVSS score of 3.7, 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-61015?
- 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-61015 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-61015?
- 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 exists within the Internal Operations component of Oracle Time and Labor (versions 12.2.3 through 12.2.15). It is classified as a low-severity issue because, although it can be reached over the network via HTTP without authentication, it is characterized by high attack complexity. A successful exploit results in an unauthorized 'read' impact, allowing the attacker to access a limited subset of data. There is no impact on data integrity or service availability. The vulnerability was addressed in the Oracle Critical Patch Update for July 2026.
Affected products
- Oracle Corporation Time and Labor 12.2.3-12.2.15
Timeline
- 2026-07-21: disclosed
- 2026-07-21: advisory