Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| safedep | gryph | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Safedep | Gryph |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f3jg-756w-gm35 | Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.106% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Safedep
Safedep gryph |
|
| Vendors & Products |
Safedep
Safedep gryph |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content | |
| Weaknesses | CWE-212 | |
| References |
| |
| Metrics |
cvssV3_1
|