CVE-2024-54137 [High] | Information Disclosure in Liboqs

liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. A correctness error has been identified in the reference implementation of the HQC key encapsulation mechanism. Due to an indexing error, part of the secret key is incorrectly treated as non-secret data. This results in an incorrect shared secret value being returned when the decapsulation function is called with a malformed ciphertext. This vulnerability is fixed in 0.12.0.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-29	0.58%	0.43%	-0.15%
2	2026-04-27	0.43%	0.58%	+0.15%
3	2026-02-12	—	0.43%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-29

0.58%

0.43%

-0.15%

2026-04-27

0.43%

0.58%

+0.15%

2026-02-12

—

0.43%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.4	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	2.2	5.2	[email protected]
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.4

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

2.2

5.2

[email protected]

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

3.6

[email protected]

OS Trackers for CVE-2024-54137

vendor	priority	summary	link
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2024-54137
`suse`	high	CVE-2024-54137 severity important: SUSE including 11 source package names (liboqs-devel-0.12.0-1.1, liboqs-devel-0.12.0-150600.3.3.1, …), 19 product×package rows across 6 product lines (SUSE Linux Enterprise Module for Basesystem 15 SP6, SUSE Linux Enterprise Module for Basesystem 15 SP7, … (6 product lines)): Fixed 19.	https://www.suse.com/security/cve/CVE-2024-54137/
`ubuntu`	medium	CVE-2024-54137 medium priority: Ubuntu has no source package entries, 0 status rows across 0 suites (none): no status rows.	https://ubuntu.com/security/CVE-2024-54137

Affected software / configurations for CVE-2024-54137

Vendor	Product	Version	Raw CPE
openquantumsafe	liboqs	< 0.12.0	cpe:2.3:a:openquantumsafe:liboqs::::::::

References for CVE-2024-54137

URL	Tags
https://github.com/open-quantum-safe/liboqs/commit/cce1bfde4e52c524b087b9687020d283fbde0f24	Patch
https://github.com/open-quantum-safe/liboqs/security/advisories/GHSA-gpf4-vrrw-r8v7	Patch Vendor Advisory

URL

CVE-2024-54137 | liboqs has a correctness error in HQC decapsulation

Exploit prediction scoring system (EPSS) score for CVE-2024-54137

Common vulnerability scoring system (CVSS) metrics for CVE-2024-54137

Weakness enumeration for CVE-2024-54137

OS Trackers for CVE-2024-54137

Affected software / configurations for CVE-2024-54137

References for CVE-2024-54137