CVE-2026-24134: StudioCMS is a server-side-rendered, Astro native, headless content management system

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

studiocms: upgrade to 0.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-24134 being exploited?

CVE-2026-24134 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-24134 affect?

CVE-2026-24134 affects studiocms. Severity is medium (CVSS 6.5). StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the "Vi

Q: How urgent is CVE-2026-24134?

Priority 35/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2026-24134 is a medium-severity flaw (CVSS 6.5) affecting studiocms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the "Visitor" role to access draft content created by Editor/Admin/Owner users. Version 0.2.0 patches the issue.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-639, CWE-862
Published	2026-01-28
Last modified	2026-06-17

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

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

Am I affected?

Timeline

2026-01-28 00:15 UTCPublished CVE record published
2026-06-17 10:22 UTCUpdated Record last modified

studiocms studiocms UPGRADE

Affected: < 0.2.0

Fixed in: 0.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy studiocms || rpm -q studiocms || studiocms --version

2. UPGRADE to 0.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade studiocms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade studiocms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-24134?

studiocms: upgrade to 0.2.0. Exact commands for each OS are on this page.

Is CVE-2026-24134 being exploited?

CVE-2026-24134 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-24134 affect?

CVE-2026-24134 affects studiocms. Severity is medium (CVSS 6.5). StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the "Vi

How urgent is CVE-2026-24134?

Priority 35/100. Public exploit reference

Related CVEs

CVE-2026-32638 LOW 2.7 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system
CVE-2026-30945 HIGH 7.1 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system
CVE-2026-30944 HIGH 8.8 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system

References

← Back to latest CVEs