Dgraph Audit Log Encryption Vulnerability

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-2023-31135: 0.15% estimated exploitation activity in the next 30 days; percentile 4.48 (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.

Impact Existing Dgraph audit logs are vulnerable to brute force attacks due to nonce collisions. All audit logs generated by versions of Dgraph <v23.0.0 are affected. Patches This issue was patched in https://github.com/dgraph-io/dgraph/pull/8323. Dgraph users should upgrade to v23.0.0. Workarounds Store existing audit logs in a secure location. For extra security, encrypt using a tool like gpg. References See https://github.com/dgraph-io/dgraph/pull/8323 for more context on the vulnerability.

Published by the source

17 May 2023, 17:07 UTC

Last modified by the source

7 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-92wq-q9pq-gw47

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

# Patch Next advisory brief: CVE-2023-31135

Advisory: Dgraph Audit Log Encryption Vulnerability
IDs: CVE-2023-31135, GHSA-92wq-q9pq-gw47
Record: https://patchnext.com/advisories/cve-2023-31135 (revision 1, source checked 26 Oct 2026, 14:59 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/dgraph-io/dgraph 23.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dgraph-io/dgraph: affected < 23.0.0; fixed in 23.0.0

## Suggested inspection (read-only)
- Go github.com/dgraph-io/dgraph: 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/dgraph-io/dgraph.
- 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-92wq-q9pq-gw47 (GitHub-reviewed advisory GHSA-92wq-q9pq-gw47 lists affected ranges: Go github.com/dgraph-io/dgraph >=0 <23.0.0)

Commands are suggestions: review each one before running it.