CVE-2026-45046

The record

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

Related vulnerabilities

• CVE-2026-111756 follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows… CWE-212
• CVE-2026-53604 nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. CWE-212
• CVE-2026-78658 IBM UCD - IBM UrbanCode Deploy 7.2 through 7.2.3.25, and 7.3 through 7.3.2.20 and IBM UCD… CWE-212
• CVE-2026-85094 The Canva Android App before 2.376.0 did not restrict the headers returned to an external… CWE-212
• CVE-2026-62900 Improper removal of sensitive information before storage or transfer in .NET allows an… CWE-212
• CVE-2024-5300 An access control bypass and information disclosure vulnerability exists in the base… CWE-212
• CVE-2026-15811 A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration… CWE-212
• CVE-2026-54421 In OpenStack Ironic through 35.0.1, when applying a PATCH to update fields in volume… CWE-212