Read the docs
TI-2022-18579 Aliases CVE-2022-39199GHSA-6cqj-6969-p57x

Lack of proper validation in immudb

Priority LOW 26CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-345.

Summary

immudb is a database with built-in cryptographic proof and verification. 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. This issue has been patched in version 1.4.1. As a workaround, 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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00293 22nd percentileScored 2026-11-07
Fix Fixed immudb (codenotary): 1.4.1github.com/codenotary/immudb (Go): 1.4.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
codenotaryimmudbbefore 1.4.11.4.1Patch availableCNA
—github.com/codenotary/immudb (Go)before 1.4.11.4.1Patch availableGHSA-6cqj-6969-p57x
  • immudb Vendorcodenotary Affected before 1.4.1 Fixed in 1.4.1 Patch available CNA
  • github.com/codenotary/immudb (Go) Vendor— Affected before 1.4.1 Fixed in 1.4.1 Patch available GHSA-6cqj-6969-p57x

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:codenotary:immudb:*:*:*:*:*:*:*:*before 1.4.1Vulnerablecodenotary
  • cpe:2.3:a:codenotary:immudb:*:*:*:*:*:*:*:* Versions before 1.4.1 Vulnerable ·codenotary

Remediation

  • Fix · CNA immudb (codenotary) Fixed in 1.4.1
  • Fix · GHSA-6cqj-6969-p57x github.com/codenotary/immudb (Go) Fixed in 1.4.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-39199
  2. 2026-10-03 Alias added: GHSA-6cqj-6969-p57x

References

  • TI-2022-16534 immundb has insufficient verification of data authenticity CVSS 3.1MEDIUM 5.4
  • TI-2024-27562 mmudb v1.9.3 was discovered to use the HTTP protocol in the ShowMetricsRaw and… CVSS 3.1HIGH 7.4

Sources