CVE-2026-45332: Automad has Broken Access Control Unauthenticated Exposure Of Administrator Bcrypt Vulnerability

HIGH
Advisory Identifier: GHSA-xm76-r88j-vm3g
CVSS 7.5
CWE-306 CWE-200
Published
Advisory Summary

CVE-2026-45332 is a HIGH (CVSS 7.5) unauthenticated exposure of administrator bcrypt vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Automad has Broken Access Control libraries in the Packagist ecosystem. The issue involves unauthenticated exposure of administrator bcrypt password hashes and totp secrets via public api endpoint. Remediation is available by upgrading affected packages to version 2.0.0-beta.28.

CVE-2026-45332 at a Glance

CVE Identifier CVE-2026-45332
GHSA Identifier GHSA-xm76-r88j-vm3g
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-306: Missing Authentication for Critical Function
Affected Product Automad has Broken Access Control
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-45332

To remediate this vulnerability, upgrade all affected Automad has Broken Access Control dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

automad/automad fixed: 2.0.0-beta.28
Upgrade automad/automad to 2.0.0-beta.28
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for automad/automad

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-45332, inspect your project dependencies for Automad has Broken Access Control:

inspect dependencies for automad/automad

Analyze the terminal output to locate any version of Automad has Broken Access Control in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.0-beta.28), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Automad has Broken Access Control, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2026-45332 Affected Automad has Broken Access Control Versions

1 component(s)
Fixed Versions:
2.0.0-beta.28
Product / Package Ecosystem Affected Versions Fixed Version
automad/automad
Packagist
≥ 2.0.0-alpha.1
< 2.0.0-beta.28
2.0.0-beta.28

References

Frequently Asked Questions

What is CVE-2026-45332?
CVE-2026-45332 is a security vulnerability in Automad has Broken Access Control involving Unauthenticated exposure of administrator bcrypt password hashes and TOTP secrets via public API endpoint under CWE-306: Missing Authentication for Critical Function.
Which Automad has Broken Access Control versions are affected?
Affected versions include releases prior to 2.0.0-beta.28 across affected packages: automad/automad.
What version fixes CVE-2026-45332?
Upgrading to 2.0.0-beta.28 (or the latest patched release for your respective branch) resolves the vulnerability.
Is automad/automad affected?
Yes, automad/automad is affected in releases prior to 2.0.0-beta.28. Upgrade your dependency to 2.0.0-beta.28 or later.
What is the CVSS score of CVE-2026-45332?
CVE-2026-45332 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-45332?
CVE-2026-45332 is classified under CWE-306: Missing Authentication for Critical Function (The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.).
How can I check Packagist dependencies for CVE-2026-45332?
Run the dependency tree command: 'inspect dependencies for automad/automad'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xm76-r88j-vm3g",
  "modified" : "2026-06-08T23:54:47Z",
  "published" : "2026-05-27T21:32:31Z",
  "aliases" : [ "CVE-2026-45332" ],
  "summary" : "Automad has Broken Access Control: Unauthenticated exposure of administrator bcrypt password hashes and TOTP secrets via public API endpoint",
  "details" : "### Summary\n\n 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.  \n\n### Details\n\nAffected version: \n - bcrypt hash exposure: `>= 2.0.0-alpha.1, <= 2.0.0-beta.27`\n - TOTP secret exposure: only `2.0.0-beta.27`\n\n### Impact\n\nAny Automad installation reachable over HTTP is at risk no prior account, credentials, or special network position are required to exploit this vulnerability.\n\nPotential impacts include:\n\n- **Credential hash exposure enabling offline brute-force or dictionary attacks:** \n  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.\n- **TOTP secret exposure:** \n  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.*  \n- **Information disclosure:** \n  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.\n\n## Remediation\n\nUpdate to version 2.0.0-beta.28 or later.\n\nThis issue was reported privately and fixed prior to public disclosure.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "automad/automad"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0-alpha.1"
      }, {
        "fixed" : "2.0.0-beta.28"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.0-beta.27"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/marcantondahmen/automad/security/advisories/GHSA-xm76-r88j-vm3g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45332"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/marcantondahmen/automad"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-306" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-27T21:32:31Z",
    "nvd_published_at" : "2026-05-28T19:16:39Z"
  }
}