# CVE-2026-68905: Hugo Blog: Unauthenticated AI Proxy Allows Abuse of Server-Side API Key

Status: published. Published: 2026-11-13. Updated: 2026-11-13.

Hugo Blog is a tech blog site. In commit 744ca15 and prior, the AI assistant proxy exposes three HTTP endpoints (POST /api/blog-assistant, POST /api/blog-search-embedding, POST /api/blog-search-rerank) without any authentication check. When deployed following the documented Nginx reverse-proxy setup, any unauthenticated remote attacker can send arbitrary requests that the proxy forwards to the upstream LLM/embedding/rerank API using the operator's server-side API key (OPENAI_API_KEY / AI_SEARCH_API_KEY). This enables unlimited quota consumption, cost exhaustion, and potential service unavailability for the operator. At time of publication, there are no publicly available patches.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- lanshi17 / hugo_blog: <= 744ca1563032e8a881390d3ed55d9a3ef2928502 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 8.2 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H; source: CNA: GitHub_M

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-306

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/lanshi17/hugo_blog/security/advisories/GHSA-pj75-r769-qjv2 (CNA: GitHub_M; x_refsource_CONFIRM)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-68905; retrieved 2026-11-13; source updated 2026-11-13

Revision: 8e4ecefdf2bd9dd343ec8e689fe042136628e54a292afd10db2676366056ff83

Canonical: https://y2.dev/cve/CVE-2026-68905

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.