# CVE-2026-22019: Missing authorization in PeopleSoft Enterprise HCM Shared Components

> Low-privileged attackers can modify or read HCM data via HTTP with user interaction, requiring patches for PeopleSoft Enterprise HCM Shared Components.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-jpmj-4mw9-x4gr

## What is CVE-2026-22019?

CVE-2026-22019 is a medium-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise HCM Shared Components, published on 21 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the PeopleSoft Enterprise HCM Shared Components product of Oracle PeopleSoft (component: Person Search).   The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise HCM Shared Components.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise HCM Shared Components, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of PeopleSoft Enterprise HCM Shared Components accessible data as well as  unauthorized read access to a subset of PeopleSoft Enterprise HCM Shared Components accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-22019?

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Hcm Shared Components.

## How do I fix CVE-2026-22019?

No fix has been published for CVE-2026-22019 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22019 being exploited?

There is no known exploitation of CVE-2026-22019 in the wild and no public exploit code.

Public exploit code:

- https://github.com/George0Papasotiriou/CVE-2026-22019-libcurl-HTTP-2-CONNECT-Tunnel-Mixup (github_poc): https://github.com/George0Papasotiriou/CVE-2026-22019-libcurl-HTTP-2-CONNECT-Tunnel-Mixup

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise HCM Shared Components

- [CVE-2021-2455](https://insights.sbomify.com/CVE-2021-2455/): Missing authorization in PeopleSoft Enterprise HCM Shared Components (medium 6.5)
- [CVE-2024-21122](https://insights.sbomify.com/CVE-2024-21122/): Missing authorization in PeopleSoft Enterprise HCM Shared Components (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22019 and fix it if it is affected.

What it is: CVE-2026-22019 is a medium-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise HCM Shared Components, published on 21 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22019 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise HCM Shared Components. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22019/ (Markdown: https://insights.sbomify.com/CVE-2026-22019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22019
- OSV: https://osv.dev/vulnerability/CVE-2026-22019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22019/
Summaries are generated and may contain mistakes; the official description above is the record.