ETK-2026-5193Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
qui versions 1.12.0 through 1.36.0 allow API-key users to redirect logging to files reachable by the service account. Depending on the release, this can expose file contents through log retrieval or enable file writes and rotation-related damage; an API key is required, and 1.36.0 additionally requires Logs: write.
mitigation
Upgrade github.com/autobrr/qui to 1.36.1, then verify and reset the configured log path if needed. Remove Logs: write from unneeded API keys, delete unused or potentially exposed keys, and rotate stored secrets if a key may have leaked.
fixed in 1.36.1
outcome
Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-22 11:51Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-5193
{ "etk_id": "ETK-2026-5193", "cve_id": null, "display_id": "ETK-2026-5193", "ghsa_id": "GHSA-9c3v-4vv2-9wrf", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "API key arbitrary file access through log paths in qui", "summary": "qui versions 1.12.0 through 1.36.0 allow API-key users to redirect logging to files reachable by the service account. Depending on the release, this can expose file contents through log retrieval or enable file writes and rotation-related damage; an API key is required, and 1.36.0 additionally requires `Logs: write`.", "mitigation": "Upgrade github.com/autobrr/qui to 1.36.1, then verify and reset the configured log path if needed. Remove `Logs: write` from unneeded API keys, delete unused or potentially exposed keys, and rotate stored secrets if a key may have leaked.", "vendor": "go", "product": "go:github.com/autobrr/qui", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 1.12.0, <= 1.36.0" ], "ecosystem": "go", "fixed_versions": [ "1.36.1" ], "package_name": "github.com/autobrr/qui", "purl": "pkg:golang/github.com/autobrr/qui" } ], "cwes": [ 73 ], "cvss_score": 8.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 10.288045683333333, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-11-22T11:51:01+00:00", "days": -0.3904450567592593, "is_lower_bound": true, "measured_at": "2026-11-22T21:13:15.657196+00:00", "url": "https://github.com/autobrr/qui/security/advisories/GHSA-9c3v-4vv2-9wrf" } } }
published 2026-11-22 12:00Z
last change 2026-11-22 21:08Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.