How severe is CVE-2024-56802?

CVE-2024-56802 has a CVSS 4.0 base score of 8.7, rated high severity.

Is CVE-2024-56802 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-56802?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-56802 have an EU (EUVD) identifier?

Yes. CVE-2024-56802 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-53435.

When was CVE-2024-56802 published?

CVE-2024-56802 was published on 2024-12-31 and last updated on 2026-06-17.

CVE-2024-56802

CVE-2024-56802 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-285.

Key facts

Severity: High (CVSS 4.0 base score 8.7)
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-53435
Weakness: CWE-285
Published: 2024-12-31
Last modified: 2026-06-17

Description

Tapir is a private Terraform registry. Tapir versions 0.9.0 and 0.9.1 are facing a critical issue with scope-able Deploykeys where attackers can guess the key to get write access to the registry. User must upgrade to 0.9.2.

Frequently asked questions

What is CVE-2024-56802?: Tapir is a private Terraform registry. Tapir versions 0.9.0 and 0.9.1 are facing a critical issue with scope-able Deploykeys where attackers can guess the key to get write access to the registry. User must upgrade to 0.9.2.
How severe is CVE-2024-56802?: CVE-2024-56802 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2024-56802 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-56802?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-56802 have an EU (EUVD) identifier?: Yes. CVE-2024-56802 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-53435.
When was CVE-2024-56802 published?: CVE-2024-56802 was published on 2024-12-31 and last updated on 2026-06-17.

References

Other CWE-285 (Improper Authorization) vulnerabilities

CVE-2025-65041 — Critical (CVSS 10.0): Improper authorization in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
CVE-2023-33189 — Critical (CVSS 10.0): Pomerium is an identity and context-aware access proxy. With specially crafted requests, incorrect authorization…
CVE-2022-2595 — Critical (CVSS 10.0): Improper Authorization in GitHub repository kromitgmbh/titra prior to 0.79.1.
CVE-2021-28799 — Critical (CVSS 10.0): An improper authorization vulnerability has been reported to affect QNAP NAS running HBS 3 (Hybrid Backup Sync. ) If…
CVE-2026-34048 — Critical (CVSS 9.9): Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to…
CVE-2026-5412 — Critical (CVSS 9.9): In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade. An authenticated…

Browse all CWE-285 (Improper Authorization) vulnerabilities →