Advisory

GHSA-f3jg-756w-gm35

Also known as: CVE-2026-45046, GO-2026-5345

Summary

Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-11 21:20 UTC
Modified
2026-06-25 19:56 UTC

Affected packages and fixes

github.com/safedep/gryph

Go · All systems

Affected

  • introduced 0, fixed 0.7.0 (semver)

Fixed versions

0.7.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences