CVE-2021-20307

9.8 CRITICAL 2% exploit odds No fix listed Memory safety

What it is

Format string vulnerability in panoFileOutputNamesCreate() in libpano13 2.9.20~rc2+dfsg-3 and earlier can lead to read and write arbitrary memory values.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
Exploit odds: 1.9% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2020-12-17 00:00 UTC ReservedThe CVE id was reserved by its CNA
2021-04-05 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 03:33 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.9% in the next 30 days (EPSS).
Severity: 9.8 CRITICAL (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2021-04-05 22:15 UTC
Last modified: 2026-06-17 03:33 UTC
Exploit probability: 1.9% · EPSS, next 30 days
Weakness: CWE-134
Record status: Modified

Affected

libpano13 Project libpano13 ≤ 2.9.19
libpano13 Project libpano13 2.9.20
Fedoraproject Fedora 32
Fedoraproject Fedora 33
Fedoraproject Fedora 34
Debian Linux 9.0

Attack profile CVSS 3.1 · 9.8

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

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

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-2021-20307.md and follow it. Check whether this project is affected by CVE-2021-20307. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record