Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-v4p2-2w39-mhrj

Apache NiFi GetAsanaObject Processor has Remote Code Execution via Unsafe Deserialization

CVSS 7.5 HighEPSS 0.0059 · 48th percentile

Published by the GitHub Advisory Database at 19 Dec 2025, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.nifi:nifi-asana-processorsMaven>=1.20.0, <2.7.02.7.0
Identifiers
GHSA-v4p2-2w39-mhrj · BIT-nifi-2025-66524 · CVE-2025-66524
Weakness (CWE)
CWE-502
Tags
Published
19 Dec 2025
Updated
23 Dec 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache NiFi's nifi-asana-processors package, versions 1.20.0 through 2.6.0, is vulnerable through the GetAsanaObject Processor, which deserializes state from its configured Distributed Map Cache Client Service without filtering. An attacker with direct access to that cache server can plant crafted state data that leads to remote code execution on the NiFi system. Upgrade to version 2.7.0, which replaces Java object serialization with JSON, or remove the GetAsanaObject Processor.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/R:U/V:C/RE:L/U:Green CNA (apache)
  • CISA KEV Not listed.
  • EPSS 0.0059, the 48th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.