# CVE-2026-45046: Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content

> Attackers with local access can read sensitive file content from logs due to improper filtering in the Gryph AI agent security library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-f3jg-756w-gm35, GO-2026-5345

## What is CVE-2026-45046?

CVE-2026-45046 is a medium-severity vulnerability in safedep gryph, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-45046?

3 open source packages ship an affected version, including github.com/safedep/gryph.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/safedep/gryph` | Go | All versions | 0.7.0 |
| `github.com/safedep/gryph` | Go | All versions | 0.7.0 |
| `github.com/safedep/gryph` | Go | All versions | 0.7.0 |

## How do I fix CVE-2026-45046?

Upgrade github.com/safedep/gryph to 0.7.0 or later.

## Is CVE-2026-45046 being exploited?

There is no known exploitation of CVE-2026-45046 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45046 and fix it if it is affected.

What it is: CVE-2026-45046 is a medium-severity vulnerability in safedep gryph, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45046 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/safedep/gryph (Go): affected all versions; fixed in 0.7.0
- github.com/safedep/gryph (Go): affected all versions; fixed in 0.7.0
- github.com/safedep/gryph (Go): affected all versions; fixed in 0.7.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45046/ (Markdown: https://insights.sbomify.com/CVE-2026-45046/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45046
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45046
- OSV: https://osv.dev/vulnerability/CVE-2026-45046

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45046/
Summaries are generated and may contain mistakes; the official description above is the record.