Vulnerabilities exploitable today
378,631in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,721
New KEV · 24H4
Exploit Today ≥ 701,652
Distribution · last window
- Critical2,396
- High8,640
- Medium6,936
- Low787
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-32166—33.2%
——10——CVE-2023-28533—33.2%
——10——CVE-2023-26528—33.2%
——10——CVE-2023-25974—33.2%
——10——CVE-2026-30653—33.2%
——10——CVE-2023-24381—33.2%
——10——CVE-2026-825616.5 MED33.2%
——10Apache NiFi 1.5.0 through 2.11.0 provide REST API methods that replace the entire contents of a Process Group using a client-supplied flow definition, covering Process Group flow replacement together with versioned flow update and rebase operations. Framework authorization for these methods was limited to read and write privileges on the Process Group itself, unlike the corresponding asynchronous update request methods, which also authorize the components encapsulated in the Process Group along with referenced Controller Services, Parameter Contexts, and Parameter Providers. As a result of the missing authorization, an authenticated user with write access to a Process Group could supply a flow definition that modifies or removes components in descendant Process Groups protected by more restrictive access policies, and could bind components to Controller Services and Parameter Contexts without authorization for those referenced components. Existing verification checks limited the impact to stopped components, and the issue applies only to deployments that use component-level authorization policies, because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which applies consistent reference resolution and component authorization across Process Group replacement and versioned flow update methods1dCVE-2025-32196—33.2%
——10——CVE-2023-23734—33.2%
——10——CVE-2023-28174—33.2%
——10——CVE-2023-28414—33.2%
——10——CVE-2022-47909—33.2%
——10——CVE-2026-0861—33.2%
——10——CVE-2023-25978—33.2%
——10——CVE-2016-6686—33.2%
——10——CVE-2025-32168—33.2%
——10——CVE-2022-39160—33.2%
——10——CVE-2023-25793—33.2%
——10——CVE-2023-24001—33.2%
——10——CVE-2023-23995—33.2%
——10——CVE-2023-24387—33.2%
——10——CVE-2022-44594—33.2%
——10——CVE-2023-22715—33.2%
——10——CVE-2022-47596—33.2%
——10——CVE-2023-22680—33.2%
——10——CVE-2025-32161—33.2%
——10——CVE-2023-23972—33.2%
——10——CVE-2023-23981—33.2%
——10——CVE-2023-24383—33.2%
——10——CVE-2024-10605—33.2%
——10——CVE-2022-45897—33.2%
——10——CVE-2022-47170—33.2%
——10——CVE-2023-23718—33.2%
——10——CVE-2014-8476—33.2%
——10——CVE-2023-23673—33.2%
——10——CVE-2023-23987—33.2%
——10——CVE-2024-47217—33.2%
——10——CVE-2023-34377—33.2%
——10——CVE-2022-47435—33.2%
——10——CVE-2022-40697—33.2%
——10——