CVE-2026-19965Public exploitNetwork attack vector

Account enumeration via password reset responses

Published Aug 17, 2026 · Updated Aug 19, 2026

Observable response discrepancy in Automad before 2.0.0-beta.33 allows remote attackers to enumerate valid accounts via password reset requests. UserController::requestPasswordResetToken in automad/src/server/Controllers/API/UserController.php returned an invalid-user error when no account matched name-or-email, while existing accounts followed a different path that could return success or a mailer failure. No authentication is required, but the practical consequence is limited to account discovery and related phishing or brute-force targeting rather than direct account takeover.

CVSS severity3.7
Low
EPSS probability0.40%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Observable response discrepancy in Automad before 2.0.0-beta.33 allows remote attackers to enumerate valid accounts via password reset requests. UserController::requestPasswordResetToken in automad/src/server/Controllers/API/UserController.php returned an invalid-user error when no account matched name-or-email, while existing accounts followed a different path that could return success or a mailer failure. No authentication is required, but the practical consequence is limited to account discovery and related phishing or brute-force targeting rather than direct account takeover.

The record

CVE
CVE-2026-19965
Published
Aug 17, 2026
Updated
Aug 19, 2026
Vendor
Automad
Product
Automad
Classifications
CWE-203, CWE-204
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.0.0-beta.0
  2. Affected versionversion=2.0.0-beta.1
  3. Affected versionversion=2.0.0-beta.10
  4. Affected versionversion=2.0.0-beta.11
  5. Affected versionversion=2.0.0-beta.12
  6. Affected versionversion=2.0.0-beta.13
  7. Affected versionversion=2.0.0-beta.14
  8. Affected versionversion=2.0.0-beta.15
  9. Affected versionversion=2.0.0-beta.16
  10. Affected versionversion=2.0.0-beta.17
  11. Affected versionversion=2.0.0-beta.18
  12. Affected versionversion=2.0.0-beta.19
  13. Affected versionversion=2.0.0-beta.2
  14. Affected versionversion=2.0.0-beta.20
  15. Affected versionversion=2.0.0-beta.21
  16. Affected versionversion=2.0.0-beta.22
  17. Affected versionversion=2.0.0-beta.23
  18. Affected versionversion=2.0.0-beta.24
  19. Affected versionversion=2.0.0-beta.25
  20. Affected versionversion=2.0.0-beta.26
  21. Affected versionversion=2.0.0-beta.27
  22. Affected versionversion=2.0.0-beta.28
  23. Affected versionversion=2.0.0-beta.29
  24. Affected versionversion=2.0.0-beta.3
  25. Affected versionversion=2.0.0-beta.30
  26. Affected versionversion=2.0.0-beta.31
  27. Affected versionversion=2.0.0-beta.32
  28. Affected versionversion=2.0.0-beta.4
  29. Affected versionversion=2.0.0-beta.5
  30. Affected versionversion=2.0.0-beta.6
  31. Affected versionversion=2.0.0-beta.7
  32. Affected versionversion=2.0.0-beta.8
  33. Affected versionversion=2.0.0-beta.9

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Automad · Automadversion=2.0.0-beta.0; version=2.0.0-beta.1; version=2.0.0-beta.10; version=2.0.0-beta.11; version=2.0.0-beta.12; version=2.0.0-beta.13; version=2.0.0-beta.14; version=2.0.0-beta.15; version=2.0.0-beta.16; version=2.0.0-beta.17; version=2.0.0-beta.18; version=2.0.0-beta.19; version=2.0.0-beta.2; version=2.0.0-beta.20; version=2.0.0-beta.21; version=2.0.0-beta.22; version=2.0.0-beta.23; version=2.0.0-beta.24; version=2.0.0-beta.25; version=2.0.0-beta.26; version=2.0.0-beta.27; version=2.0.0-beta.28; version=2.0.0-beta.29; version=2.0.0-beta.3; version=2.0.0-beta.30; version=2.0.0-beta.31; version=2.0.0-beta.32; version=2.0.0-beta.4; version=2.0.0-beta.5; version=2.0.0-beta.6; version=2.0.0-beta.7; version=2.0.0-beta.8; version=2.0.0-beta.9

Published CVSS scores

2.6VulDBAV:N/AC:H/Au:N/C:P/I:N/A:N
2.9VulDBCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
3.7VulDBCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-203Observable Discrepancy
CWE-204Observable Response Discrepancy

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo