EUVD-2026-32624
GHSA-f3jg-756w-gm35
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Local SQLite file access requires local filesystem privileges (AV:L, PR:L); only confidentiality is impacted as file content is passively exposed with no integrity or availability effect.
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
Gryph implements logging levels that determine what content is logged to a local sqlite database. The README incorrectly mentions that the default log level is minimal while it is standard. Source code review shows sensitive file-write content remains in the stored payload as ContentPreview, OldString, or NewString at the default standard logging level and at full. This leads to logging of potentially sensitive file content in the local sqlite database, violating Gryphs sensitive file filter and log level contracts.
Impact
Potentially sensitive data accessed or written by coding agents may be logged to local sqlite database. Users of Gryph are affected ONLY if their local sqlite database is stolen or exported to remote system with the assumption that no sensitive data is logged.
Patches
Fixed in v0.7.0
AnalysisAI
Sensitive file content written by coding agents is inadvertently persisted to a local SQLite database in Gryph versions up to and including 0.6.0 due to a payload redaction failure in the logging subsystem. The ContentPreview, OldString, and NewString fields of file-write tool payloads bypass the product's own sensitive file filter at both the default 'standard' and 'full' log levels - a behavior compounded by incorrect README documentation claiming the default level was 'minimal'. No active exploitation is confirmed (not in CISA KEV), and EPSS is 0.01% (2nd percentile), reflecting the local-access prerequisite and niche deployment footprint. A vendor patch is available in v0.7.0.
Technical ContextAI
Gryph (CPE: pkg:go/github.com_safedep_gryph) is a Go-based coding agent framework that intercepts and observes tool calls made by AI agents - such as Claude Code - and stores structured event data in a local SQLite database. The logging architecture defines multiple verbosity levels (minimal, standard, full) with corresponding payload redaction rules. CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer) identifies the root cause: the payload filter for file-write events fails to strip the ContentPreview, OldString, and NewString fields before persisting to the database at the 'standard' and 'full' levels. These fields can contain actual file content, including source code or configuration data touched by the agent. The vulnerability is a contract violation - the sensitive file filter is documented to prevent this class of exposure, but the implementation does not enforce it for file-write payload fields.
RemediationAI
Upgrade Gryph to v0.7.0, which includes commit 61159f7b ('fix: Redact events and enforce log levels') that corrects the payload filter to properly strip sensitive content before persistence. The release is available at https://github.com/safedep/gryph/releases/tag/v0.7.0. For users unable to upgrade immediately, a compensating control is to restrict filesystem permissions on the Gryph SQLite database file so that only the owning user process can read it - this limits opportunistic access but does not address the root logging failure. Alternatively, setting the log level explicitly to 'minimal' if that level correctly suppresses payload content in the affected version may reduce exposure, though this should be verified against source code since the README documentation was confirmed inaccurate. Users should audit any existing SQLite databases created by Gryph <= 0.6.0 for retained sensitive content and treat those files as potentially containing sensitive data.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today