Gryph, a security layer for AI coding agents, stored sensitive file‑write contents in its local sqlite database at default and full logging levels. Prior to version 0.7.0, the logging mechanism did not strip out content designated as sensitive, so any file write operation could inadvertently leave a preview of the data in the database. As a result, an attacker with access to the local database could retrieve potentially confidential information that was intended to be excluded from logs.

The vulnerability affects all safedep Gryph deployments running a release before 0.7.0. No further version granularity is specified, so any instance of Gryph installed prior to updating to 0.7.0 is susceptible. The issue is tied to the default logging configuration, which applies to the standard log level and above.

The CVSS score of 5.5 categorizes the weak as medium severity, and the EPSS is not available, so no quantified exploitation likelihood can be assigned. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires local access to the machine running Gryph, as the attacker must read the sqlite database. Based on the description, it is inferred that the attack vector is local or requires an insider or compromised administrator. Because sensitive data is written to disk, the potential impact is confidential data leakage rather than system compromise.