Approved changes feed: RSS · Atom
cpe:2.3:a:safedep:gryph:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Safedep (bff13e60-2986-5e73-b798-91522cd70280) |
|---|---|
| Product | Gryph (5738d0d5-807f-5984-bf9a-9d2b1251a694) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-45046 |
vulnerable | 2026-06-08 08:05:11.440867 |
Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content
MEDIUM (5.5)
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.
Published: 2026-05-27T18:24:23.410Z
Updated: 2026-05-27T18:52:43.894Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.