CVE-2026-39816: The optional extension component TinkerpopClientService is missing the Restricted annotation with the Execute

This month

HIGH 8.8WATCHLISTUPGRADE

CVE-2026-39816 is a high-severity flaw (CVSS 8.8) affecting nifi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The optional extension component TinkerpopClientService is missing the Restricted annotation with the Execute Code Required Permission in Apache NiFi 2.0.0-M1 through 2.8.0. The TinkerpopClientService supports configuration of ByteCode Submission for the Script Submission Type, enabling Groovy Script execution in the service prior to submitting the query. The missing Restricted annotation allows users without the Execute Code Permission to config

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-05-08
Last modified	2026-10-26

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-08 14:16 UTCPublished CVE record published
2026-10-26 19:10 UTCUpdated Record last modified

apache nifi UPGRADE

Affected: >= 2.0.0 and < 2.9.0

Fixed in: 2.9.0

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy nifi || rpm -q nifi || nifi --version

2. UPGRADE to 2.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nifi

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nifi

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison nifi sudo apt install nifi=<VERSION_BEFORE_2.0.0> sudo apt-mark hold nifi

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list nifi sudo dnf downgrade nifi-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add nifi

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39816?

nifi: upgrade to 2.9.0. Exact commands for each OS are on this page.

Is CVE-2026-39816 being exploited?

CVE-2026-39816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39816 affect?

CVE-2026-39816 affects nifi. Severity is high (CVSS 8.8). The optional extension component TinkerpopClientService is missing the Restricted annotation with the Execute Code Required Permission in Apache NiFi 2.0.0-M1 through 2.8.0. The TinkerpopClientService supports configuration of ByteCode Subm

How urgent is CVE-2026-39816?

Priority 50/100. High severity; On your watchlist

Related CVEs

CVE-2026-44913 HIGH 7.2 UPGRADE Improper escaping of database table names in the CaptureChangeMySQL Processor included with Apache NiFi 1.2.0
CVE-2026-44914 HIGH 7.2 UPGRADE Apache NiFi 1.12.0 through 2.9.0 are missing authorization when replacing Process Groups that include extensio
CVE-2026-44911 MEDIUM 6.3 UPGRADE Authorization handling for component configuration verification requests in Apache NiFi 1.15.0 through 2.9.0 a
CVE-2026-54665 MEDIUM 5.3 UPGRADE Apache NiFi 0.0.1 through 2.9.0 support building qualified URLs from one of several HTTP request headers that
CVE-2026-68979 CRITICAL 9.8 UPGRADE Apache NiFI 1.10.0 through 2.10.0 provide a Parameter Context update REST API method that does not enforce aut

References

← Back to latest CVEs