Lack of proper validation of server UUID can be used by the server to trick the client to accept invalid proofs

Exploitation

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

CVSS

5.8 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N

EPSS

• CVE-2022-39199: 0.29% estimated exploitation activity in the next 30 days; percentile 22.03 (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 immudb client SDKs use server's UUID to distinguish between different server instance so that the client can connect to different immudb instances and keep the state for multiple servers. SDK does not validate this uuid and can accept any value reported by the server. A malicious server can change the reported UUID tricking the client to treat it as a different server thus accepting a state completely irrelevant to the one previously retrieved from the server. Patches The following Go SDK versions are not vulnerable: | SDK | Version | |-------|------------| | go | 1.4.1 | Workarounds When initializing an immudb client object, a custom state handler can be used to store the state. Providing custom implementation that ignores the server UUID can be used to ensure that even if the server changes the UUID, client will still consider it to be the same server. For more information If you have any questions or comments about this advisory: Open a discussion in immudb Discussions…

Published by the source

21 Nov 2022, 20:38 UTC

Last modified by the source

14 Feb 2023, 21:39 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6cqj-6969-p57x

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

# Patch Next advisory brief: CVE-2022-39199

Advisory: Lack of proper validation of server UUID can be used by the server to trick the client to accept invalid proofs
IDs: CVE-2022-39199, GHSA-6cqj-6969-p57x
Record: https://patchnext.com/advisories/cve-2022-39199 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/codenotary/immudb 1.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/codenotary/immudb: affected < 1.4.1; fixed in 1.4.1

## Suggested inspection (read-only)
- Go github.com/codenotary/immudb: 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/codenotary/immudb.
- 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-6cqj-6969-p57x (GitHub-reviewed advisory GHSA-6cqj-6969-p57x lists affected ranges: Go github.com/codenotary/immudb >=0 <1.4.1)

Commands are suggestions: review each one before running it.