PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-78166 provectus CVE debrief

A security flaw has been discovered in provectus kafka-ui up to 0.7.2, affecting the function executeSmartFilterTest of the file kafka-ui-api/src/main/java/com/provectus/kafka/ui/controller/MessagesController.java in the Groovy Code Handler, leading to code injection. The attack may be launched remotely. This issue was reported to the project early but has not yet received a response. Defenders should assess exposure and prioritize verification of the Groovy Code Handler. The vulnerability allows remote code injection through the Groovy Code Handler, impacting kafka-ui deployments. Limited vendor response has been noted.

Vendor
provectus
Product
kafka-ui
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-24
Original CVE updated
2026-10-12
Advisory published
2026-08-24
Advisory updated
2026-10-12

Who should care

Defenders responsible for kafka-ui deployments should assess exposure and prioritize verification of the Groovy Code Handler. Operators, platform administrators, vulnerability managers, and security teams may be impacted by this vulnerability. They should review kafka-ui presence, assess Groovy Code Handler exposure, and monitor for potential remote attacks. Remediation priority is unknown due to limited vendor response.

Why it matters

CVE-2026-78166 is a code injection vulnerability in provectus kafka-ui up to 0.7.2. Defenders should prioritize verifying kafka-ui deployments and assessing Groovy Code Handler exposure to prevent potential remote attacks.

  • Remote attackers may inject code through the Groovy Code Handler
  • Defenders must verify kafka-ui presence and Groovy Code Handler exposure
  • Remediation priority is unknown due to limited vendor response

Technical summary

The function executeSmartFilterTest in the file kafka-ui-api/src/main/java/com/provectus/kafka/ui/controller/MessagesController.java of the component Groovy Code Handler is vulnerable to code injection, allowing remote attackers to inject code. The affected product is provectus kafka-ui up to 0.7.2. Defenders should prioritize verifying kafka-ui deployments and assessing Groovy Code Handler exposure to prevent potential remote attacks. The vulnerability is confirmed but vendor guidance is pending. kafka-ui deployments should be verified for exposure.

Defensive priority

Defenders should prioritize verifying the presence of kafka-ui in their environment and assessing the exposure of the Groovy Code Handler.

Recommended defensive actions

  • Verify the presence of kafka-ui in the environment
  • Assess the exposure of the Groovy Code Handler
  • Monitor for potential remote attacks
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets
  • Plan vendor-supported updates or mitigations through normal change control

Evidence notes

The CVE record and NVD entry provide information about the vulnerability, but the vendor's response and remediation status are unknown. Defenders should verify kafka-ui presence, assess Groovy Code Handler exposure, and monitor for potential remote attacks. Evidence is limited to CVE and NVD details. No additional information is available on exploitability or remediation status.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-78166 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-78166

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-78166 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-78166

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.