How severe is GHSA-v3vc-6qcv-4vrx?

No CVSS score has been assigned to GHSA-v3vc-6qcv-4vrx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v3vc-6qcv-4vrx?

GHSA-v3vc-6qcv-4vrx affects the following packages: org.apache.nifi:nifi-framework-core (Maven), org.apache.nifi:nifi-framework-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v3vc-6qcv-4vrx?

Update org.apache.nifi:nifi-framework-core to 1.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3vc-6qcv-4vrx is resolved across your whole dependency graph.

How do I detect GHSA-v3vc-6qcv-4vrx in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.nifi:nifi-framework-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v3vc-6qcv-4vrx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-v3vc-6qcv-4vrx actively exploited in the wild?

No public exploit code has been indexed for GHSA-v3vc-6qcv-4vrx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v3vc-6qcv-4vrx?

GHSA-v3vc-6qcv-4vrx has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v3vc-6qcv-4vrx?

GHSA-v3vc-6qcv-4vrx is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v3vc-6qcv-4vrx published, and has it been updated?

GHSA-v3vc-6qcv-4vrx was published on February 11, 2025 and was last updated on February 11, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Apache NiFi: Potential Insertion of Sensitive Parameter…

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v3vc-6qcv-4vrx.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.nifi:nifi-framework-core☕org.apache.nifi:nifi-framework-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache NiFi 1.16.0 through 1.28.0 and 2.0.0-M1 through 2.0.0-M4 include optional debug logging of Parameter Context values during the flow synchronization process. An authorized administrator with access to change logging levels could enable debug logging for framework flow synchronization, causing the application to write Parameter names and values to the application log. Parameter Context values may contain sensitive information depending on application flow configuration. Deployments of Apache NiFi with the default Logback configuration do not log Parameter Context values. Upgrading to Apache NiFi 2.0.0 or 1.28.1 is the recommendation mitigation, eliminating Parameter value logging from the flow synchronization process regardless of the Logback configuration.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.nifi:nifi-framework-core`	≥ 1.16.0&&< 1.28.1	1.28.1`org.apache.nifi:nifi-framework-core:1.28.1`
☕Maven	`org.apache.nifi:nifi-framework-core`	≥ 2.0.0-M1&&< 2.0.0	2.0.0`org.apache.nifi:nifi-framework-core:2.0.0`

Affected Products

1 product · 17 configurations

Application

nifiapache

≥ 1.16.0 && < 1.28.1

1 version

2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.nifi:nifi-framework-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.nifi:nifi-framework-core to 1.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3vc-6qcv-4vrx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Apache NiFi 1.16.0 through 1.28.0 and 2.0.0-M1 through 2.0.0-M4 include optional debug logging of Parameter Context values during the flow synchronization process. An authorized administrator with access to change logging levels could enable debug logging for framework flow synchronization, causing the application to write Parameter names and values to the application log. Parameter Context values may contain sensitive information depending on application flow configuration. Deployments of Apache NiFi with the default Logback configuration do not log Parameter Context values. Upgrading to Apac

O3 Security · Impact-Aware SCA

Is GHSA-v3vc-6qcv-4vrx in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Apache NiFi: Potential Insertion of Sensitive Parameter Values in Debug LogGHSA-v3vc-6qcv-4vrx