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

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

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

Q: Is CVE-2026-32638 being exploited?

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

CVE-2026-32638 affects studiocms. Severity is low (CVSS 2.7). StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should

Q: How urgent is CVE-2026-32638?

Priority 23/100. Public exploit reference

Routine

LOW 2.7UPGRADE

CVE-2026-32638 is a low-severity flaw (CVSS 2.7) 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. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request `rank=owner` and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent `

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	2.7 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-639
Published	2026-03-18
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-03-18 21:16 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

studiocms studiocms UPGRADE

Affected: < 0.4.4

Fixed in: 0.4.4

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.4.4 (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-32638?

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

Is CVE-2026-32638 being exploited?

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

CVE-2026-32638 affects studiocms. Severity is low (CVSS 2.7). StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should

How urgent is CVE-2026-32638?

Priority 23/100. Public exploit reference

Related CVEs

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
CVE-2026-24134 MEDIUM 6.5 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system

References

← Back to latest CVEs