dbcve.org
NifiApplication · Apache

CVE-2025-66524

HIGH · 8.8 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to 2.7.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache NiFi 1.20.0 through 2.6.0 include the GetAsanaObject Processor, which requires integration with a configurable Distribute Map Cache Client Service for storing and retrieving state information. The GetAsanaObject Processor used generic Java Object serialization and deserialization without filtering. Unfiltered Java object deserialization does not provide protection against crafted state information stored in the cache server configured for GetAsanaObject. Exploitation requires an Apache NiFi system running with the GetAsanaObject Processor, and direct access to the configured cache server. Upgrading to Apache NiFi 2.7.0 is the recommended mitigation, which replaces Java Object serialization with JSON serialization. Removing the GetAsanaObject Processor located in the nifi-asana-processors-nar bundle also prevents exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache NiFi 1.20.0-2.6.0 GetAsanaObject Processor uses unfiltered Java Object serialization/deserialization with a Distribute Map Cache Client Service. An attacker with direct access to the configured cache server can store malicious serialized Java objects that will be deserialized by the processor, potentially leading to remote code execution.

MitigationUpgrade to Apache NiFi 2.7.0 which replaces Java Object serialization with JSON serialization, or remove the GetAsanaObject Processor from the nifi-asana-processors-nar bundle and restart NiFi.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NifiApplication
Affected:>= 1.20.0, < 2.7.0= 2.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed NiFi version
    Check the NiFi version by accessing the NiFi UI footer, or using the API endpoint /nifi-api/systemDiagnostics, or checking the nifi-assembly jar file name in the lib directory
    Affected if The version is 1.20.0 through 2.6.0 inclusive, or exactly 2.7.0
  2. Determine if the GetAsanaObject processor is deployed
    In the NiFi UI, search for 'GetAsanaObject' in the processor list, or check if the nifi-asana-processors-nar bundle is present in the NiFi nar directory
    Affected if The GetAsanaObject processor is available or the asana NAR bundle is loaded
  3. Check if Distribute Map Cache Client Service is configured
    For any GetAsanaObject processor instance, open the processor configuration and inspect the 'DistributeMap Cache Client Service' property in the Properties tab
    Affected if A Distribute Map Cache Client Service is selected and configured
  4. Verify the cache client service type
    Navigate to the Controller Services, find the configured DistributeMapCache Client Service, and check its implementation type in the service configuration
    Affected if A DistributeMapCache Client Service is used (any implementation such as DistributedMapCacheClient, RedisDistributedMapCacheClient, etc.)
  5. Confirm the serialization mechanism
    There is no direct detection method; this check is informational. In versions 1.20.0-2.6.0 and 2.7.0, the GetAsanaObject processor uses Java Object serialization to interact with the cache service
    Affected if Running an affected version with the GetAsanaObject processor configured to use a DistributeMapCache Client Service

You are affected if you are running NiFi 1.20.0-2.6.0 or 2.7.0 AND have a GetAsanaObject processor configured with a DistributeMapCache Client Service pointing to a cache server accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.0 or later
Fixed in 2.7.0
Interim mitigation

Upgrade to Apache NiFi 2.7.0 which replaces Java Object serialization with JSON serialization, or remove the GetAsanaObject Processor from the nifi-asana-processors-nar bundle and restart NiFi.

Recommended fix High confidence

Apache NiFi 2.7.0 or later stable release

  1. 1. Review the Apache NiFi release notes for version 2.7.0 to understand the changes and any migration requirements.
  2. 2. Back up your current NiFi configuration, flow definitions, and any custom processors.
  3. 3. Download Apache NiFi 2.7.0 (or a later stable release if available) from the official Apache NiFi downloads page.
  4. 4. Stop the running NiFi instance gracefully.
  5. 5. Install the new NiFi 2.7.0 binaries.
  6. 6. Restore your backed-up configuration and flow definitions to the new installation.
  7. 7. Start the NiFi instance and verify the GetAsanaObject Processor functions correctly with the new version.
  8. 8. Verify that the Distribute Map Cache Client Service now uses JSON serialization instead of Java Object serialization.
Caveat Review release notes for potential breaking changes between 1.20.0-2.6.0 and 2.7.0, particularly around the GetAsanaObject Processor and serialization behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nifi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66524 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data