The Presenton Electron application started local frontend and backend services, with authentication disabled by the tested desktop default. A separate file-serving path exposed the app data directory, which the researcher says contained plaintext model provider credentials, session material and presentation artifacts. The October 3 controlled report showed…
Inspect the ClaimsCase · DiggingBeagle record
Presenton desktop exposed stored AI provider keys through its local API
Presenton security issues report that the desktop build defaulted to DISABLE_AUTH=true and served its application-data directory over unauthenticated local HTTP, including files containing AI provider API keys.
Researcher-reported behavior in v0.9.11-beta and a Windows distribution; no confirmed real victim or independently verified exploit against all desktop platforms.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade C
- Remediation
- mitigation available
- AI role
- AGAINST AI
Basis and provenance
Two issue reports describe separate local service authorization and static app-data exposure defects in the tested desktop build. Programmatic theft from another web origin has additional browser and network preconditions. Impact remains unrated because the evidence does not supply a calibrated scale for this Case.
Assessed Nov 1, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-2026-NOV01-PRESENTON-LOCAL-AI-SECRETS-1 · CLM-2026-NOV01-PRESENTON-LOCAL-AI-SECRETS-2 · Presenton issue 973: exposed local configuration and credential directory · Presenton issue 972: desktop build disables authentication on local APIs
At a glance
Assess the reported tool or model action separately from the side effect actually observed.
Read the implicationsResearcher-reported behavior in v0.9.11-beta and a Windows distribution; no confirmed real victim or independently verified exploit against all desktop platforms.
Limits and uncertaintyFull account
The Presenton Electron application started local frontend and backend services, with authentication disabled by the tested desktop default. A separate file-serving path exposed the app data directory, which the researcher says contained plaintext model provider credentials, session material and presentation artifacts. The October 3 controlled report showed local downloads, while cross-origin programmatic theft required additional browser-origin or rebinding conditions. The issues are related but technically distinct: the authentication default opens a request boundary, and the static mount makes sensitive files reachable.
The local API and its file-serving route are separate preconditions. A service may have no login boundary but still be reachable only from the device; data theft by an unrelated website adds origin and rebinding questions. A complete test should first establish which endpoint reads the stored model key and then test whether an untrusted browser can reach that endpoint.
Mechanism and trust boundary
- 01
Step
Claims & evidence
CLM-2026-NOV01-PRESENTON-LOCAL-AI-SECRETS-1Presenton security issues report that the desktop build defaulted to DISABLE_AUTH=true and served its application-data directory over unauthenticated local HTTP, including files containing AI provider API keys.supported
Basis: reported finding
- supportsPresenton issue 972: desktop build disables authentication on local APIsprimary disclosure
Presenton GitHub issue 972, desktop DISABLE_AUTH behavior, reproduction and issue 973
CLM-2026-NOV01-PRESENTON-LOCAL-AI-SECRETS-2Presenton issue 973 documents an /app_data static directory mapping that exposed local configuration, a SQLite credentials database, logs and generated outputs in the tested desktop build.supported
Basis: reported finding
- supportsPresenton issue 973: exposed local configuration and credential directoryprimary disclosure
GitHub issue 973, 1.1 Static directory, 3 Reproduction and local HTTP 200 tests
Implications
Assess the reported tool or model action separately from the side effect actually observed.
Controls and mitigations
- Turn on authentication, avoid exposing service directories through static routes, move and protect API keys in an OS credential store, and validate local request origins against DNS rebinding.
Unknowns and contradictions
- Researcher-reported behavior in v0.9.11-beta and a Windows distribution; no confirmed real victim or independently verified exploit against all desktop platforms.
Sources and citation
Material revision history
- Nov 1, 2026 · Canonical change recorded · new in release · revision 211