Blombooru: administrator image-proxy server-side request forgery
Impact
Blombooru versions prior to 1.40.0 have a server-side request forgery vulnerability in the administrator-only `GET /proxy-image` endpoint, allowing authenticated administrators to access internal services and potentially disclose sensitive information. The endpoint fetches a URL without meaningful validation. Administrator authentication is required.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
mrblomblo · GitHub_M
blombooru
1 range
mrblomblo · GitHub_M
blombooru
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 1.40.0
Other versions: unknown
Original source description
Blombooru is a self-hosted personal booru for organizing and tagging private image collections. Prior to 1.40.0, the administrator-only GET /proxy-image endpoint, exposed as /api/booru-import/proxy-image, accepts a url query parameter and fetches it server-side without meaningful destination validation. proxy_image() in backend/app/routes/booru_import.py only checks whether the value starts with http, then uses get_client_for_url or requests.get and streams the response. Private, loopback and link-local addresses are not blocked, and automatically followed redirects can move a request from a trusted domain to an internal address. An authenticated administrator can enumerate internal services and access cloud instance metadata, potentially disclosing IAM credentials and crossing the application's intended cloud or network trust boundary. The reporter also observed a hanging recursive self-request. Administrator authentication remains a prerequisite; this is not an anonymous proxy. This issue is fixed in version 1.40.0.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-57448View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.