vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-6272

HIGH
8.5
CVSS Score
Published: April 24, 2026 at 08:28 AM UTC
Updated: October 26, 2026 at 10:10 PM UTC
1 product affected across 1 vendorKuksa

Using Eclipse KUKSA - Databroker by Eclipse Foundation?

Get instant alerts when new vulnerabilities affect Eclipse KUKSA - Databroker - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH8.5
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest. 1. Obtain any valid token with only read scope. 2. Connect to the normal production gRPC API (kuksa.val.v2). 3. Open OpenProviderStream. 4. Send ProvideSignalRequest for a target signal ID. 5. Wait for the broker to forward GetProviderValueRequest. 6. Reply with attacker-controlled GetProviderValueResponse. 7. Other clients performing GetValue / GetValues for that signal receive forged data.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Kuksa· Eclipse
90%
0.5.0 ≤ v ≤ 0.6.00.5.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

Source: cverecord
https://gitlab.eclipse.org/security/cve-assignment/-/issues/98

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.5HIGHeclipse
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-306

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card