# CVE-2026-19906: pkp pkp-lib API Key Generation APIProfileForm.php setData entropy

> Insufficient entropy in API key generation allows attackers to predict keys, potentially bypassing authentication controls in PKP software.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-gccx-9qmf-hrf5

## What is CVE-2026-19906?

CVE-2026-19906 is a medium-severity vulnerability in pkp-lib, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in pkp pkp-lib 3.3.0/3.4.0/3.5.0. This vulnerability affects the function setData of the file classes/user/form/APIProfileForm.php of the component API Key Generation. Executing a manipulation of the argument apiKey can lead to insufficient entropy. The attack may be performed from remote. This attack is characterized by high complexity. It is stated that the exploitability is difficult. This patch is called 529b5df878e571ccc727647f7748eafc1466b041. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-331 (Insufficient Entropy), CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2026-19906 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19906 is a medium-severity vulnerability in pkp-lib, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19906 in the wild and no public exploit code.

Affected product: pkp-lib. 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-19906/ (Markdown: https://insights.sbomify.com/CVE-2026-19906/index.md)
```

## Sources

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

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