CVE-2026-34372

CVE-2026-34372 is a medium-severity security vulnerability in sulu/sulu (composer), affecting versions >= 1.0.0, < 2.6.22. It is fixed in 2.6.22, 3.0.5.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Sulu checks fix permissions for subentities endpoints

Workarounds

Create a Symfony Request Listener checking the permissions for the specific roles.

Resources

Github Advisory: https://github.com/sulu/sulu/security/advisories/GHSA-6h7h-m7p5-hjqp

Impact

A user which has permission for the Sulu Admin via atleast one role could have access to the subentities of contacts via the admin API without even have permission for contacts.

Affected versions

sulu/sulu (>= 1.0.0, < 2.6.22) sulu/sulu (>= 3.0.0, < 3.0.5)

Security releases

sulu/sulu → 2.6.22 (composer) sulu/sulu → 3.0.5 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

The issue was patched in release 2.6.22 and 3.0.5.

Frequently Asked Questions

  1. What is CVE-2026-34372? CVE-2026-34372 is a medium-severity security vulnerability in sulu/sulu (composer), affecting versions >= 1.0.0, < 2.6.22. It is fixed in 2.6.22, 3.0.5.
  2. Which versions of sulu/sulu are affected by CVE-2026-34372? sulu/sulu (composer) versions >= 1.0.0, < 2.6.22 is affected.
  3. Is there a fix for CVE-2026-34372? Yes. CVE-2026-34372 is fixed in 2.6.22, 3.0.5. Upgrade to this version or later.
  4. Is CVE-2026-34372 exploitable, and should I be worried? Whether CVE-2026-34372 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-34372 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-34372?
    • Upgrade sulu/sulu to 2.6.22 or later
    • Upgrade sulu/sulu to 3.0.5 or later

Other vulnerabilities in sulu/sulu

Stop the waste.
Protect your environment with Kodem.