CVE-2026-6272
A client holding only a read JWT scope can still register itself as a signal provider through the...
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
- Record
CVE-2026-6272- CVSS 4.0
- 8.5 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H - Weakness
- CWE-306
- Updated
- 2026-11-02
EUVDEUVD-2026-25409
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
- Record
EUVD-2026-25409- CVSS 4.0
- 8.5 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-66v8-c34p-jmrm
A client holding only a read JWT scope can still register itself as a signal provider through the...
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
- Record
GHSA-66v8-c34p-jmrm- CVSS 4.0
- 8.5 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Weakness
- CWE-306
- Updated
- 2026-11-02
NVD
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
- Record
CVE-2026-6272- CVSS 4.0
- 8.5 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Weakness
- CWE-306
- Updated
- 2026-11-02
OSV
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.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
- Record
CVE-2026-6272- CVSS 4.0
- 8.5 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H - Weakness
- CWE-306
- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-6272 is a high vulnerability (CVSS 8.5) in Eclipse Foundation Kuksa - Databroker, published April 24, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.32%, the 24th percentile. No source names a fixed version.