How severe is GHSA-xm76-r88j-vm3g?

GHSA-xm76-r88j-vm3g has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xm76-r88j-vm3g?

GHSA-xm76-r88j-vm3g affects the following packages: automad/automad (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xm76-r88j-vm3g?

Update automad/automad to 2.0.0-beta.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xm76-r88j-vm3g is resolved across your whole dependency graph.

How do I detect GHSA-xm76-r88j-vm3g in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for automad/automad. 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-xm76-r88j-vm3g 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-xm76-r88j-vm3g?

O3 pinpoints whether GHSA-xm76-r88j-vm3g 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-xm76-r88j-vm3g actively exploited in the wild?

No public exploit code has been indexed for GHSA-xm76-r88j-vm3g 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-xm76-r88j-vm3g?

GHSA-xm76-r88j-vm3g has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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-xm76-r88j-vm3g?

GHSA-xm76-r88j-vm3g is classified as Information Exposure (CWE-200), Missing Authentication (CWE-306). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xm76-r88j-vm3g published, and has it been updated?

GHSA-xm76-r88j-vm3g was published on May 27, 2026 and was last updated on June 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-xm76-r88j-vm3g

HIGH

Automad has Broken Access Control: Unauthenticated exposure of administrator bcrypt password hashes and TOTP secrets via public API endpoint

Also known asCVE-2026-45332

Published

May 27, 2026

Updated

Jun 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk22th percentile0.00%

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.

Blast Radius

1 pkg affected

🐘automad/automad

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A Broken Access Control vulnerability allows an unauthenticated attacker to retrieve the bcrypt password hash of every administrator account with a single POST request. The /_api/user-collection/create-first-user setup endpoint remains publicly accessible once initial configuration is complete and returns full serialized user data in the JSON response body.

Details

Affected version:

bcrypt hash exposure: >= 2.0.0-alpha.1, <= 2.0.0-beta.27
TOTP secret exposure: only 2.0.0-beta.27

Impact

Any Automad installation reachable over HTTP is at risk no prior account, credentials, or special network position are required to exploit this vulnerability.

Potential impacts include:

Credential hash exposure enabling offline brute-force or dictionary attacks: bcrypt password hashes for every administrator are returned in a single unauthenticated response. While hashes are not plaintext passwords, the salt embedded in the hash is not secret it is visible in the response. Administrators using common or weak passwords are at direct risk of having their plaintext password recovered.
TOTP secret exposure: The TOTP secret is included in the response starting with version 2.0.0-beta.27, the first release introducing TOTP-based two-factor authentication. If an attacker successfully recovers a plaintext password, two-factor authentication can be bypassed entirely. Only version 2.0.0-beta.27 is affected by this specific issue.
Information disclosure: The response discloses the absolute filesystem path to the configuration directory. While the directory structure is publicly documented, the absolute server path may expose environment-specific information.

Remediation

Update to version 2.0.0-beta.28 or later.

This issue was reported privately and fixed prior to public disclosure.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`automad/automad`	≥ 2.0.0-alpha.1&&< 2.0.0-beta.28	2.0.0-beta.28

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for automad/automad. 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 automad/automad to 2.0.0-beta.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xm76-r88j-vm3g 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-xm76-r88j-vm3g 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-xm76-r88j-vm3g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A Broken Access Control vulnerability allows an unauthenticated attacker to retrieve the bcrypt password hash of every administrator account with a single POST request. The `/_api/user-collection/create-first-user` setup endpoint remains publicly accessible once initial configuration is complete and returns full serialized user data in the JSON response body. ### Details Affected version: - bcrypt hash exposure: `>= 2.0.0-alpha.1, <= 2.0.0-beta.27` - TOTP secret exposure: only `2.0.0-beta.27` ### Impact Any Automad installation reachable over HTTP is at risk no prior acc

O3 Security · Impact-Aware SCA

Is GHSA-xm76-r88j-vm3g in your dependencies?

O3 detects GHSA-xm76-r88j-vm3g across Packagist 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