Loading story…
Apache NiFi disclosed a high-severity authorization flaw, tracked as CVE-2026-25903, that allows a lower-privileged user to modify configuration properties of Restricted extension components after they have been added to a flow by a more privileged user. The issue affects NiFi versions 1.1.0 through 2.7.2 and stems from missing authorization checks during component property updates: the framework enforced the extra privileges required to add a Restricted component, but did not consistently re-check the component’s restricted status when updating it, enabling an authorization bypass (CWE-862). Potential impact includes tampering with dataflow logic and, depending on the component and environment, enabling unsafe actions such as triggering sensitive operations or altering processing behavior.
Risk is conditional on deployments that implement distinct authorization levels for Restricted components; installations that do not differentiate authorization levels are described as not subject to this specific bypass because standard write permissions remain the effective security boundary. Upgrading to NiFi 2.8.0 is the recommended mitigation, and the issue was reported via responsible disclosure (credited to David Handermann in reporting). CVE records also reference public advisories and include a CVSS v4.0 vector indicating network reachability and high potential impact, while noting prerequisites such as the need for a privileged user to have already introduced the Restricted component into the flow.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
Apache identified Apache NiFi 2.8.0 as the fixed version for CVE-2026-25903 and advised users to upgrade. The remediation closes the gap where restricted-status permissions were enforced during component addition but not during later updates.
Apache NiFi disclosed CVE-2026-25903, a missing authorization check flaw that lets lower-privileged users modify configuration properties of previously added Restricted components. The issue affects NiFi versions 1.1.0 through 2.7.2 and can enable unauthorized workflow or command-related changes depending on deployment permissions.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Apache NiFi fixed **CVE-2026-39816**, a high-severity flaw that lets authenticated users execute arbitrary code without the `EXECUTE_CODE` permission when certain optional graph extensions are installed, particularly `nifi-other-graph-services-nar`. The issue affects NiFi versions **2.0.0-M1 through 2.8.0** and stems from the `TinkerpopClientService`, which can compile and run user-supplied **Groovy** code before submitting a graph query. Apache attributed the bug to a missing restricted annotation tied to the Execute Code required permission, creating a privilege-boundary bypass in deployments using TinkerPop graph query features. The vulnerability was reported by **John Walker of ZeroPath** and tracked as `NIFI-15800`, with Apache addressing it in **NiFi 2.9.0**. ZeroPath said the flaw reflects a mismatch in NiFi’s privilege model, where graph query functionality was not treated as a code-execution path even though TinkerPop’s native query mode can trigger server-side code execution; the researchers also published a proof of concept showing shell access on a vulnerable server. Organizations running affected NiFi deployments are advised to upgrade to **2.9.0 or later** or remove the impacted optional graph-related NAR extensions if an upgrade cannot be completed immediately.
Jun 29, 2026
Apache disclosed **CVE-2026-59083**, a vulnerability in Tomcat's `RewriteValve` caused by incorrect URL decoding of hex-encoded characters that can let attackers bypass security controls in some configurations. The issue is classified as **CWE-177** and was described as low severity by Apache, though the CVE record notes network attackability with low attack complexity, no privileges required, and no user interaction. Apache said the flaw affects supported Tomcat branches **11.0.0-M1 through 11.0.23**, **10.1.0-M1 through 10.1.56**, and **9.0.0.M1 through 9.0.119**, with reports also listing **8.5.0 through 8.5.100** as affected. Apache and downstream advisories urged users to upgrade to fixed releases **11.0.24**, **10.1.57**, or **9.0.120**, while warning that older unsupported versions may also be vulnerable; versions before **8.0.0** were noted as unaffected in the oss-security disclosure. The vulnerability was published through Apache security pages, the Apache mailing list, and `oss-security`, with the CVE entry updated to include affected-version details, a CVSS v3.1 vector, and a CISA SSVC assessment.
Jul 15, 2026
n8n published security advisories for multiple supported release branches after disclosure of several vulnerabilities, including a critical flaw tracked as **`CVE-2026-56348`**. The CVE affects versions before **`2.20.0`** and allows an authenticated user to abuse the **`POST /rest/dynamic-node-parameters/options`** endpoint to bypass **Allowed HTTP Request Domains** restrictions, causing the server to send credential-bearing HTTP requests to unauthorized hosts and potentially exfiltrate sensitive authentication data. The issue is remotely exploitable and impacts environments where users can access affected dynamic node functionality. The broader advisory set also covers additional n8n weaknesses in releases prior to **`2.28.1`**, **`2.27.4`**, and **`1.123.61`**, including another Allowed HTTP Request Domains bypass through the **AI Agents MCP Connector**, prototype pollution via workflow credentials that can lead to unauthenticated user and project enumeration, cross-issuer token exchange account binding caused by subject-only identity resolution, and a shared credential header leak through HTTP request pagination expressions. The Canadian Centre for Cyber Security urged administrators to review the advisories, upgrade to the patched versions, restrict access to exposed endpoints where possible, and monitor for unauthorized outbound requests that could indicate credential leakage.
Jun 29, 2026