Skip to main content
VulnerabilityPublished Updated

CVE-2026-90474: samanhappy mcphub · Improper Authentication

Affects samanhappy mcphubSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High : upgrade to 1.0.32 soon.

Data as of 28 Oct 2026, 05:12 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.32
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade mcphub and samanhappy/mcphub to 1.0.32.

Affected software

ProductAffectedFixed in
samanhappymcphubAffected
  • <1.0.32
Fixed in
  • 1.0.32
GitHubsamanhappy/mcphubpkg:github/samanhappy/mcphubOther threatsAffected
  • <1.0.32
Fixed in
  • 1.0.32

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MCPHub to version 1.0.32 or later, where this vulnerability is fixed. Ensure that client authentication is enabled and PKCE enforcement is mandatory in the OAuth 2.0 authorization server configuration to prevent unauthorized token redemption.

Description

MCPHub before 1.0.32 contains an authentication bypass vulnerability in its embedded OAuth 2.0 authorization server where client authentication is disabled by default and PKCE enforcement is optional. Attackers who obtain an authorization code through interception can redeem it for access tokens without providing a client secret or PKCE verifier, gaining access to victim accounts and their privileges.

References

Community reviews

Loading reviews…