CVE-2026-45046
Published:May 27, 2026
Updated:June 11, 2026
Gryph provides a security layer for AI coding agents. Prior to 0.7.0, 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. This vulnerability is fixed in 0.7.0.
Affected Packages
https://github.com/safedep/gryph.git (GITHUB):
Affected version(s) >=v0.1.0 <v0.7.0Fix Suggestion:
Update to version v0.7.0github.com/safedep/gryph (GO):
Affected version(s) >=v0.0.0-20260131135922-c2d455b70508 <v0.7.0Fix Suggestion:
Update to version v0.7.0Related Resources (4)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.8
Attack Vector
LOCAL
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
NONE
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.5
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Weakness Type (CWE)
Improper Removal of Sensitive Information Before Storage or Transfer
EPSS
Base Score:
0.01