CVE-2006-4790

What it is

verify.c in GnuTLS before 1.4.4, when using an RSA key with exponent 3, does not properly handle excess data in the digestAlgorithm.parameters field when generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents GnuTLS from correctly verifying X.509 and other certificates that use PKCS, a variant of CVE-2006-4339.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2006-09-14 19:07 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:29 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.6% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2006-09-14 19:07 UTC

Last modified

2026-06-16 22:29 UTC

Exploit probability

2.6% · EPSS, next 30 days

Record status

Modified

Affected

• Gnu Gnutls 1.0.17
• Gnu Gnutls 1.0.18
• Gnu Gnutls 1.0.19
• Gnu Gnutls 1.0.20
• Gnu Gnutls 1.0.21
• Gnu Gnutls 1.0.22
• Gnu Gnutls 1.0.23
• Gnu Gnutls 1.0.24

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-4790.md and follow it. Check whether this project is affected by CVE-2006-4790. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge