CVE Intelligence
High Info disclosure

CVE-2021-33560 — Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks...

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

Published Jun 8, 2021 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 2.3% (30-day exploitation probability)+12
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
2.34%
ahead of 83% of scored CVEs · Oct 14, 2026
Affects
Debian
Debian Linux and 7 more
CVSS base
7.5
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — dev.gnupg.org (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Fedoraproject Fedora, Gnupg Libgcrypt…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 9.0 Vulnerable NIST National Vulnerability Database
Fedoraproject Fedora version 33version 34 Vulnerable NIST National Vulnerability Database
Gnupg Libgcrypt < 1.8.8≥ 1.9.0 and < 1.9.3 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Binding Support Function version 1.11.0 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Network Function Cloud Native Environment version 1.9.0version 1.10.0 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Network Repository Function version 1.14.0version 1.15.0version 1.15.1 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Network Slice Selection Function version 1.8.0 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Service Communication Proxy version 1.15.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-203 · Observable Discrepancy

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.34%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · gnupg/libgcrypt, debian/debian linux, fedoraproject/fedora, oracle/communications cloud native core binding support func
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2021
  • CVE published
    Jun 8, 2021 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

19 on the record

Elsewhere on this site

Debian
every CVE for this vendor
Info disclosure
same class
CWE-203
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD Jul 3, 2026
  • CVE-2026-56968 Use of Uninitialized Resource in Gnu Sasl Jun 23, 2026
  • CVE-2026-54231 Abrt: unsanitized systemd journal content written to dump directory files enables content injection Jun 13, 2026
  • CVE-2026-54230 Abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites Jun 13, 2026
  • CVE-2026-49975 Apache HTTP Server: mod_http2 denial of service Jun 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2021-33560 is "Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks...", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 2.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.