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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-45046: 0.11% estimated exploitation activity in the next 30 days; percentile 1.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

11 May 2026, 21:20 UTC

Last modified by the source

8 Jun 2026, 23:53 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f3jg-756w-gm35

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45046

Advisory: Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content
IDs: CVE-2026-45046, GHSA-f3jg-756w-gm35
Record: https://patchnext.com/advisories/cve-2026-45046 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/safedep/gryph 0.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/safedep/gryph: affected <= 0.6.0; fixed in 0.7.0

## Suggested inspection (read-only)
- Go github.com/safedep/gryph: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/safedep/gryph.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f3jg-756w-gm35 (GitHub-reviewed advisory GHSA-f3jg-756w-gm35 lists affected ranges: Go github.com/safedep/gryph >=0 <=0.6.0)

Commands are suggestions: review each one before running it.