What is CVE-2026-19906?

CVE-2026-19906 is pkp pkp-lib API Key Generation APIProfileForm.php setData entropy. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-331 CWE-331; CWE-330 CWE-330.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-19906. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-19906 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-19906 using CVSS 3.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

lowRemote Code Execpublic exploit

CVE-2026-19906

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

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.

Published Aug 15, 2026Updated Aug 15, 2026Sources: NVD, pkp (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

pkp

3 products listed

CVSS base

3.7

low · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade pkp-lib to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
pkp	pkp-lib	3.3.0	Vulnerable
pkp	pkp-lib	3.4.0	Vulnerable
pkp	pkp-lib	3.5.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
3.7	CVSS 3.1	low	2.2	1.4	NVD
2.6	CVSS 2.0	low	4.9	2.9	vuldb.com (CNA)
6.3	CVSS 4.0	medium	—	—	pkp (CNA)
3.7	CVSS 3.1	low	—	—	pkp (CNA)
3.7	CVSS 3.0	low	—	—	pkp (CNA)
2.6	CVSS 2.0	low	—	—	pkp (CNA)

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-330 · Use of Insufficiently Random Values

Other
Bypass Protection Mechanism
Gain Privileges or Assume Identity

Mitigation: Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a random enough number.

CWE-331 · Insufficient Entropy

Bypass Protection Mechanism
Other

Mitigation: Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.::

Weakness & attack patterns

CWE-331
CWE-330

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-59 · Session Credential Falsification through Prediction

T1110Brute Force
T1552.004Unsecure Credentials: Private Keys

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /3.4.0/3.5.0, /user/form/APIProfileForm.php.
Prioritize edge telemetry for network-reachable pkp-lib.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 3.7 (AV:N)
Aug 15, 2026 · NVD
Initial · CVE published
Aug 15, 2026 · NVD
Reported · Advisory disclosed
Aug 14, 2026 · pkp
Reported · VulDB entry created
Aug 14, 2026 · pkp
Reported · VulDB entry last update
Aug 14, 2026 · pkp

References

7 on the record

github.com/pkp/pkp-lib/
Exploit, Third Party Advisory
github.com/pkp/pkp-lib/commit/529b5df878e571ccc727647f7748eafc1466b041
Exploit, Third Party Advisory
github.com/pkp/pkp-lib/issues/12951
Exploit, Third Party Advisory
vuldb.com/cve/CVE-2026-19906
Vendor Advisory
vuldb.com/submit/870828
Vendor Advisory
vuldb.com/vuln/390119
Vendor Advisory
vuldb.com/vuln/390119/cti
Vendor Advisory

Coverage

1 story from the feeds we poll

CVE-2026-19906
vuldb.com · Aug 14, 2026

Elsewhere on this site

pkpevery CVE for this vendor
Remote Code Execsame class
CWE-331other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-19906 is pkp pkp-lib API Key Generation APIProfileForm.php setData entropy, a low vulnerability affecting pkp-lib from pkp. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-19906. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 3.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.