How severe is GHSA-3xcq-8mjw-h6mx?

No CVSS score has been assigned to GHSA-3xcq-8mjw-h6mx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3xcq-8mjw-h6mx?

GHSA-3xcq-8mjw-h6mx affects the following packages: @strapi/content-type-builder (npm), @strapi/plugin-content-type-builder (npm). Ecosystems affected: npm.

How do I fix GHSA-3xcq-8mjw-h6mx?

Update @strapi/content-type-builder to 5.33.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3xcq-8mjw-h6mx is resolved across your whole dependency graph.

How do I detect GHSA-3xcq-8mjw-h6mx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/content-type-builder. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3xcq-8mjw-h6mx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3xcq-8mjw-h6mx?

O3 pinpoints whether GHSA-3xcq-8mjw-h6mx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3xcq-8mjw-h6mx actively exploited in the wild?

No public exploit code has been indexed for GHSA-3xcq-8mjw-h6mx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3xcq-8mjw-h6mx?

GHSA-3xcq-8mjw-h6mx has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3xcq-8mjw-h6mx?

GHSA-3xcq-8mjw-h6mx is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3xcq-8mjw-h6mx published, and has it been updated?

GHSA-3xcq-8mjw-h6mx was published on May 13, 2026 and was last updated on May 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-3xcq-8mjw-h6mx

GHSA-3xcq-8mjw-h6mx is a SQL Injection vulnerability in @strapi/content-type-builder. O3 Security confirms whether GHSA-3xcq-8mjw-h6mx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Strapi Vulnerable to SQL Injection in Content Type Builder

Also known asCVE-2026-22599

Published

May 13, 2026

Updated

May 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@strapi/content-type-buildernpm

140Kdownloads / week

@strapi/plugin-content-type-buildernpm

38Kdownloads / week

Description

Summary of CVE-2026-22599 Vulnerability Details

CVE: CVE-2026-22599
CVSS v3.1 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N (9.3 — Critical)
Affected Versions: @strapi/content-type-builder <=5.33.1 (v5), @strapi/plugin-content-type-builder <=4.26.0 (v4)
How to Patch: Immediately update your Strapi to >=5.33.2 (v5) or >=4.26.1 (v4)

Description of CVE-2026-22599

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: true }] caused the value to be passed directly into Knex's db.connection.raw() during schema migration without sanitization, allowing arbitrary statement execution at the database layer. Depending on the database engine, this enabled arbitrary file read via database utility functions, denial of service via forced server crash on schema-migration error, and on engines that permit external program execution, remote code execution against the database server.

The patch addresses this by restricting all Content-Type Builder write APIs to development mode only. Production deployments running v5.33.2 or later return 404 for requests against /content-type-builder/content-types and related endpoints, removing the network-reachable attack surface entirely.

IoC's for CVE-2026-22599

Indicators that an instance running an unpatched version may have been exploited:

HTTP access logs containing POST or PUT requests to /content-type-builder/content-types from a non-internal source. Regex pattern: (POST|PUT)\s+/content-type-builder/
Database server logs containing unexpected DEFAULT clause values that reference filesystem-access or program-execution helper functions of your database engine
Strapi server crashes immediately following a content-type creation or update, observed as the Node process exiting during the schema-migration step
Files appearing under unexpected paths on the database host that match content-type DEFAULT values from the application
Newly-created content-types named or shaped to extract specific data (attribute names like passwd, etc, env, config)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@strapi/content-type-builder`	≥ 5.0.0&&< 5.33.2	5.33.2
📦npm	`@strapi/plugin-content-type-builder`	≥ 4.0.0&&< 4.26.1	4.26.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/content-type-builder. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @strapi/content-type-builder to 5.33.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3xcq-8mjw-h6mx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3xcq-8mjw-h6mx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3xcq-8mjw-h6mx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary of CVE-2026-22599 Vulnerability Details - CVE: CVE-2026-22599 - CVSS v3.1 Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N` (9.3 — Critical) - Affected Versions: `@strapi/content-type-builder` <=5.33.1 (v5), `@strapi/plugin-content-type-builder` <=4.26.0 (v4) - How to Patch: Immediately update your Strapi to >=5.33.2 (v5) or >=4.26.1 (v4) ### Description of CVE-2026-22599 A database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated administrator could inject arbitrary database statements through the `colu

O3 Security · Impact-Aware SCA

Is GHSA-3xcq-8mjw-h6mx in your dependencies?

O3 detects GHSA-3xcq-8mjw-h6mx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works