CVE-2026-68905: lanshi17 hugo_blog · Missing Authentication for Critical Functionality
Affects lanshi17 hugo_blogSource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 13 Nov 2026, 20:18 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| lanshi17hugo_blog | Affected
| Fixed in– |
AI-suggested
At the time of publication, no patches or official fixes are available. Operators should implement authentication controls on the exposed endpoints to prevent unauthorized access. Until a vendor patch is released, restricting access via network controls such as IP whitelisting or firewall rules around these endpoints can help mitigate the risk.
Description
CVE-2026-68905 is a vulnerability in the lanshi17 hugo_blog project where three HTTP endpoints exposed by the AI assistant proxy lack authentication. This allows unauthenticated remote attackers to send arbitrary requests that are forwarded to upstream APIs using the operator's server-side API keys, potentially leading to quota exhaustion and service disruption. No patches are available at the time of publication.