# CVE-2026-82958: Code injection in Eclipse Ditto

> Attackers can inject JSON structures via unescaped headers in Eclipse Ditto to override access policies, gaining unauthorized control over digital twins.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-cgfq-3fv9-5c44

## What is CVE-2026-82958?

CVE-2026-82958 is a high-severity code injection vulnerability in Eclipse Ditto, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Eclipse Ditto versions [1.3.0, 3.9.6], the ImplicitThingCreationMessageMapper of the connectivity service builds a CreateThing command by substituting placeholder values (e.g. {{ header:device_id }}) resolved from inbound message headers into a pre-configured JSON "thing" template as raw, un-escaped strings, and then parses the resulting string as JSON. Because the placeholder engine performs no JSON escaping and is unaware of the surrounding JSON string context, a resolved value containing a double-quote character can break out of its string and inject additional JSON structure.

When a connection is configured to use this mapper with a template that reflects a header whose value a publishing device can control (for example an MQTT 5 user property, an AMQP 1.0 application property, or a Kafka record header), an attacker able to publish on that connection can inject an inline _policy object. The inline policy overrides the administrator-configured policyId, letting the attacker assign an arbitrary access-control policy to the newly created digital twin — gaining full read/write access to it and potentially revoking the legitimate owner's access, with no administrator interaction.

Exploitation requires all of the following: the connection uses the (non-default) ImplicitThingCreation mapper; its template reflects an attacker-controllable header; and, for the policy-override impact, the connection's authorization subjects are permitted to create policies (the default). Deployments that restrict the connection's subjects to thing creation only via the entity-creation configuration are not affected by the policy-override impact.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-82958?


## How do I fix CVE-2026-82958?

No fix has been published for CVE-2026-82958 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82958 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82958 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82958 and fix it if it is affected.

What it is: CVE-2026-82958 is a high-severity code injection vulnerability in Eclipse Ditto, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82958 exists.

Affected product: Eclipse Ditto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82958/ (Markdown: https://insights.sbomify.com/CVE-2026-82958/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82958
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82958
- OSV: https://osv.dev/vulnerability/CVE-2026-82958

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82958/
Summaries are generated and may contain mistakes; the official description above is the record.