6.4 KiB
title, type, status, created, updated, verified_on, review_after, confidence, tags, sources
| title | type | status | created | updated | verified_on | review_after | confidence | tags | sources | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Live Secrets Stored Verbatim in Mnemosyne Rows, Session Transcripts and Two Cron Prompts (2026-11-05) | incident | open | 2026-11-06 | 2026-11-06 | 2026-11-06 | 2026-11-13 | high |
|
|
Live Secrets Stored Verbatim in Mnemosyne Rows, Session Transcripts and Two Cron Prompts (2026-11-05)
Status: OPEN - found by the nightly audit (2026-11-05 window), not remediated. No key was rotated, no memory row deleted and no cron prompt scrubbed. This page records where the values live and how many rows carry them; no credential value appears on it (SCHEMA rule 1 - record where secrets live, never their values).
What was found
Three exposures, all verified by direct read on 2026-11-06 00:22-00:50 AWST.
1. Live .env values as plaintext rows in the memory store
17 rows of ~/.hermes/mnemosyne/data/mnemosyne.db carry values from ~/.hermes/.env. Method: every
TEXT/BLOB column of every table, plus the FTS mirrors, scanned for exact substring membership.
| Key (name only) | Rows | Columns carrying it |
|---|---|---|
TELEGRAM_BOT_TOKEN |
4 | memories.content x1, episodic_memory.content x1, gists.text x1, fts_episodes.content x1 |
MATTERMOST_TOKEN |
6 | memories.content x1, episodic_memory.content x1, gists.text x2, memoria_facts.context_snippet x1, fts_episodes.content x1 |
HERMES_CUSTOM_OMNIROUTE_20128_API_KEY |
7 | memories.content x2, working_memory.content x1, episodic_memory.content x1, gists.text x1, fts_episodes.content x1, fts_working.content x1 |
- Every hit is in
mnemosyne.db(27.7 MB, live). Theepisodic_memory.dbandmemoria_facts.dbfiles beside it are 0-byte legacy stubs (created 2026-10-27) - the tables with those names live insidemnemosyne.db. Nothing was found in the cross-agent shared surface (~/.hermes/data/shared/mnemosyne.db). - The rotation snapshots carry them too. Seven uncompressed snapshots under
~/.hermes/mnemosyne/backups/(mnemosyne-pre-orphan-cleanup.db,-20261004_030035,-20261011_030046,-20261018_030021,-20261025_030108,-20261101_030033,-20261105_140314) contain all three values in full; the 2026-09-27 snapshot predates them. The.db.gzsnapshots are compressed and were not substring-tested - assume the same until proven otherwise.
2. One live key embedded verbatim in two cron prompts
The CAMOFOX_API_KEY value appears in the prompt text of two enabled jobs in
~/.hermes/cron/jobs.json:
0e753e9720fd- Facebook Birthday Monthly Scrape (0 9 1 * *)fad5a86979d4- Facebook Birthday Weekly Registry Sync (0 3 * * 1)
Consequence: the same value is inside delivery records in ~/.hermes/cron/deliveries.db. Of the 10 .db
files under ~/.hermes/config-backup/ (six of them 0-byte), cron/deliveries.db is the only one that
carries any tested value; cron/executions.db, cron/notepad.db and data/shared/mnemosyne.db carry none.
3. Session transcripts hold all four values
~/.hermes/state.db (1.7 GB, the session store) contains all four values. Measured as 4 MB chunks
containing the value: CAMOFOX_API_KEY 178, MATTERMOST_TOKEN 64,
HERMES_CUSTOM_OMNIROUTE_20128_API_KEY 61, TELEGRAM_BOT_TOKEN 22. This is the most likely origin of
exposure 1 - the memory-capture path writes from session text, so a session in which a key was printed
becomes a memory row - and it is itself a plaintext at-rest store that deleting memory rows does not clear.
Why it matters
- Mnemosyne rows are recall material: they are pulled into a session's context by semantic or FTS match, so a secret in a row is a secret in a prompt - echoable into any cron delivery (Telegram, Mattermost, email), any subagent transcript, or the cross-agent shared surface.
- It turns every backup into a credential copy. Deleting the rows does not recall the copies; rotation is the only remedy that fully closes it.
jobs.jsonis the fleet's source of truth and is exported and examined routinely; a prompt-embedded key is exposed to anything that reads job definitions.state.dbis the fleet's largest artifact (1.7 GB) and is copied into snapshots and repair backups.
Origin (inferred - not established)
Almost certainly the memory-capture path storing verbatim session text in which a key was printed by a
tool call or a .env read. Not verified: no capture-time or delivery-time redaction filter is known to
exist, and the affected rows carry no marker distinguishing them from ordinary content.
Remediation options (proposed, none executed)
- Rotate the three Mnemosyne-exposed values and the Camofox key - touches live services; needs a maintenance window and explicit approval.
- Redact or forget the affected rows (
mnemosyne forget <id>per row), then re-take the rotation snapshots so the superseded values leave the backup set. - Move the two Facebook Birthday jobs off prompt-embedded keys - read the key from the environment or config at run time.
- Add capture-time and delivery-time redaction so
.envvalues cannot enter memory rows, job prompts or delivery records again. - Decide a retention/serialisation policy for
state.db- it currently holds every transcript verbatim at 1.7 GB.
Verification evidence
- Key names and lengths extracted from
~/.hermes/.env(values never printed), then matched as exact substrings across every TEXT/BLOB column of every table inmnemosyne.dbincluding the FTS mirrors - row counts as tabled. - Byte-membership scans of the 10
.dbfiles under~/.hermes/config-backup/, the shared-surface DB, the livecron/deliveries.db+cron/executions.db, the seven uncompressed Mnemosyne rotation snapshots, and a chunked scan ofstate.db. json.dumps()membership test of each value against every job object injobs.json.- Not done: no value was printed, logged or written to any wiki page; nothing was deleted, rotated or scrubbed.
See also
- infrastructure/credentials-map - where secrets live, by design
- systems/mnemosyne - the memory store whose tables carry them
- systems/scheduled-tasks - the Facebook Birthday jobs' schedules
- SCHEMA - the no-values rule this violates