Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The maintainer identified an error in the libyaml fuzzers. It is not possible to reproduce nor exploit the issue.
Conclusion & alert: This CVE is rejected; it is not tracked as an active vulnerability. Mandatory action: Do not treat as an active exposure for patching queues—follow the CVE record status and authoritative vendor or program statements only.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2024-04-03 | — | 0.04% | — |
Full EPSS history (1 record total)
CVSS metrics for this CVE.
No CVSS data in dataset for this CVE.
| vendor | priority | summary | link |
|---|---|---|---|
redhat
|
— | — | https://access.redhat.com/security/cve/CVE-2024-3205 |
suse
|
high | CVE-2024-3205 severity important: SUSE including 4 source package names (libyaml, libyaml-0-2, libyaml-devel, perl-YAML-LibYAML), 102 product×package rows across 32 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 12 SP5, … (32 product lines)): Known Not Affected 102. | https://www.suse.com/security/cve/CVE-2024-3205/ |
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| No affected products in dataset. | |||
| URL | Tags |
|---|---|
| No references in dataset. | |