HUGO_BLOG · CVE-2026-68905 · Package
NO FIX YET · SEE WHAT TO DO
Hugo Blog's AI assistant proxy exposes three endpoints with no authentication check. Any remote visitor can send arbitrary requests that the server forwards to the upstream LLM, embedding and rerank APIs using the operator's own API key.
first public Jul 5, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running lanshi17/hugo_blog at commit 744ca15 or earlier that run the AI assistant proxy (npm run ai-proxy) with a server-side OPENAI_API_KEY or AI_SEARCH_API_KEY and expose /api/* publicly, as the documented Nginx setup does. Anyone can then spend the operator's LLM quota. Sites without the proxy, or with those endpoints blocked or authenticated upstream, can skip it.
Not affected if ai-proxy-not-running, auth-required, default-config, endpoints-blocked-at-proxy
Who cares hugo-blog, llm-api-key, nginx, self-hosted
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.