CVE-2026-22599: Strapi is an open source headless content management system

Q: How do I fix CVE-2026-22599?

strapi: upgrade to 4.26.1, 5.33.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-22599 being exploited?

CVE-2026-22599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-22599 affect?

CVE-2026-22599 affects strapi. Severity is high (CVSS 7.2). Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API.

This month

HIGH 7.2UPGRADE

CVE-2026-22599 is a high-severity flaw (CVSS 7.2) affecting strapi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated administrator could inject arbitrary database statements through the `column.defaultTo` attribute when creating or modifying a content type. Setting `defaultTo` as a tuple `[value, { isRaw: tr

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-89
Published	2026-05-14
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: strapi

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-14 19:16 UTCPublished CVE record published
2026-10-26 14:10 UTCUpdated Record last modified

strapi strapi UPGRADE

Affected: >= 4.0.0 and < 4.26.1 · >= 5.0.0 and < 5.33.2

Fixed in: 4.26.1, 5.33.2

Safe to downgrade to: a release before 4.0.0

1. Check installed version

npm ls strapi

2. UPGRADE to 4.26.1

npm install strapi@">=4.26.1"

3. If no update is available yet, DOWNGRADE to a release before 4.0.0

npm view strapi versions npm install strapi@"<4.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-22599?

strapi: upgrade to 4.26.1, 5.33.2. Exact commands for each OS are on this page.

Is CVE-2026-22599 being exploited?

CVE-2026-22599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-22599 affect?

CVE-2026-22599 affects strapi. Severity is high (CVSS 7.2). Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API.

How urgent is CVE-2026-22599?

Priority 42/100. High severity

Software pages

Strapi vulnerabilities

Related CVEs

CVE-2026-22706 MEDIUM 6.5 UPGRADE Strapi is an open source headless content management system
CVE-2026-22707 MEDIUM 5.4 UPGRADE Strapi is an open source headless content management system
CVE-2026-57997 MEDIUM 4.8 UPGRADE Strapi users-permissions plugin fails to restrict JWT algorithms when plugin::users-permissions.jwt.algorithm
CVE-2023-22894 MEDIUM 4.9 EXPLOITED UPGRADE Strapi Cleartext Storage of Sensitive Information Vulnerability

References

← Back to latest CVEs