ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-100362

V8 OAuth2 Username Enumeration

Published Oct 12, 2026 · catalog updated Oct 12, 2026 · V8 OAuth2 Username Enumeration

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-100362. A missing EPSS score is not a low risk. Compare V8 OAuth2 Username Enumeration with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (V8 OAuth2 Username Enumeration).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Not established
Affected products
See sources for product scope

### Summary The V8 OAuth2 password-grant endpoint returns distinct error messages for invalid usernames versus invalid passwords, allowing any unauthenticated attacker to enumerate all valid CRM user accounts ### Impact This is a username enumeration vulnerability. Any unauthenticated remote attacker can determine which usernames exist in the CRM by sending password-grant requests to the V8 OAuth2 endpoint and observing the differing error messages. This directly enables targeted attacks against confirmed accounts - password spraying, credential stuffing, social engineering, and brute-force. All SuiteCRM 8.x instances exposing the /legacy/Api/V8/OAuth2 endpoint are affected.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-100362

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-100362. A missing EPSS score is not a low risk. Compare V8 OAuth2 Username Enumeration with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-204. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

SuiteCRM security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 12, 2026 · Maintainer security tabs

    Detected

    ### Summary The V8 OAuth2 password-grant endpoint returns distinct error messages for invalid usernames versus invalid passwords, allowing any unauthenticated attacker to enumerate all valid CRM user accounts ### Impact This is a username enumeration vulnerability. Any unauthenticated remote attacker can determine which usernames exist in the CRM by sending password-grant requests to the V8 OAuth2

Sources

  • CVE.orgVulnerability recordCVE-2026-100362

    Official CVE identifier

    cve.org
  • Maintainer security tabsVendor advisoryGHSA-rc46-hjjp-4jv5

    ### Summary The V8 OAuth2 password-grant endpoint returns distinct error messages for invalid usernames versus invalid passwords, allowing any unauthenticated attacker to enumerate all valid CRM user accounts ### Impact This is a username enumeration vulnerability. Any unauthenticated remote attacker can determine which usernames exist in the CRM by sending password-grant requests to the V8 OAuth2

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 2, 2026
  • Maintainer security tabsNov 1, 2026