CVE-2026-62518
published 2026-07-21CVE-2026-62518: Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are…
PriorityP350high7.6CVSS 3.1
AVNACLPRLUINSUCLIHAL
EPSS
0.32%
22.9th percentile
Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Production Scheduling. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Production Scheduling accessible data as well as unauthorized read access to a subset of Oracle Production Scheduling accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Production Scheduling. CVSS 3.1 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L).
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gnu | tar | >= 0 < 0.4.45 | 0.4.45 |
| gnu | tar | >= 0.0.0-0 < 0.4.45 | 0.4.45 |
| oracle | e-business_suite | 12.2.3 – 12.2.15 | — |
| oracle_corporation | oracle_production_scheduling | 12.2.3 – 12.2.15 | — |
CVSS provenance
nvdv3.17.6HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
ghsa8.1HIGH
osv8.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Oracle Production Scheduling up to 12.2.15 Internal Operations privileges management
vuldb·2026-08-08·CVSS 7.6
CVE-2026-62518 [HIGH] Oracle Production Scheduling up to 12.2.15 Internal Operations privileges management
A vulnerability was found in Oracle Production Scheduling up to 12.2.15. It has been classified as critical. The impacted element is an unknown function of the component Internal Operations. Performing a manipulation results in improper privilege management.
This vulnerability is identified as CVE-2026-62518. The attack can be initiated remotely. There is not any exploit available.
GHSA
Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations).
ghsa_unreviewed·2026-07-22
CVE-2026-62518 [HIGH] CWE-200 Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations).
Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Production Scheduling. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Production Scheduling accessible data as well as unauthorized read access to a subset of Oracle Production Scheduling accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Production Scheduling. CVSS 3.1 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/A
GHSA
tar-rs incorrectly ignores PAX size headers if header size is nonzero
ghsa·2026-03-20·CVSS 8.1
CVE-2026-33055 [HIGH] CWE-843 tar-rs incorrectly ignores PAX size headers if header size is nonzero
tar-rs incorrectly ignores PAX size headers if header size is nonzero
### Summary
As part of [CVE-2025-62518](https://www.cve.org/CVERecord?id=CVE-2025-62518) the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header.
However, it was missed at the time that this project (the original Rust `tar` crate) had a conditional logic that skipped the PAX size header in the case that the base header size was nonzero - almost the inverse of the astral-tokio-tar issue.
The problem here is that *any* discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers.
In this case, the tar-rs (Rust `tar`) crate is an outlier in checking for the header si
OSV
tar-rs incorrectly ignores PAX size headers if header size is nonzero
osv·2026-03-19·CVSS 8.1
CVE-2026-33055 tar-rs incorrectly ignores PAX size headers if header size is nonzero
tar-rs incorrectly ignores PAX size headers if header size is nonzero
Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX
size header in cases where the base header size is nonzero.
As part of [CVE-2025-62518][astral-cve], the [astral-tokio-tar]
project was changed to correctly honor PAX size headers in the case where it
was different from the base header. This is almost the inverse of the
astral-tokio-tar issue.
Any discrepancy in how tar parsers honor file size can be used to create
archives that appear differently when unpacked by different archivers. In this
case, the tar-rs (Rust tar) crate is an outlier in checking for the header size
— other tar parsers (including e.g. Go [`archive/tar`][go-tar]) unconditionally
use the PAX size override. This can affect
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2025-62518 kata-containers: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
bugzilla·2025-10-21·CVSS 8.1
CVE-2025-62518 [HIGH] CVE-2025-62518 kata-containers: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
CVE-2025-62518 kata-containers: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy t
Bugzilla
CVE-2025-62518 trustee-guest-components: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
bugzilla·2025-10-21·CVSS 8.1
CVE-2025-62518 [HIGH] CVE-2025-62518 trustee-guest-components: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
CVE-2025-62518 trustee-guest-components: astral-tokio-tar Vulnerable to PAX Header Desynchronization [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's
2026-07-21
Published