# CVE-2026-110109: JetLinks Community through 2.10.0 Missing Authorization via Product-Level Transparent Codec Save

> Attackers with query access can overwrite product codecs, controlling message decoding and encoding for all devices in that product.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-6q8r-vgvx-r98p

## What is CVE-2026-110109?

CVE-2026-110109 is a high-severity missing authorization vulnerability in JetLinks Community, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JetLinks Community through 2.10.0 contains a missing authorization vulnerability that allows users with only query access on transparent-codec to overwrite product codecs via POST /device/transparent-codec/{productId}. Because the endpoint lacks @SaveAction, attackers can save arbitrary codec providers and configurations, controlling how transparent messages are decoded and encoded for every device of that product.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110109 being exploited?

There is no known exploitation of CVE-2026-110109 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110109 is a high-severity missing authorization vulnerability in JetLinks Community, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110109 in the wild and no public exploit code.

Affected product: JetLinks Community. 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-110109/ (Markdown: https://insights.sbomify.com/CVE-2026-110109/index.md)
```

## Sources

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

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