# CVE-2026-112356: GFI KerioConnect < 10.0.9p2 XSS via Link Auto-Formatter


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-53x6-q8p5-wm6r

## What is CVE-2026-112356?

CVE-2026-112356 is a medium-severity vulnerability in GFI KerioConnect, published on 28 Oct 2026. 

### Official description

GFI KerioConnect (Kerio Connect) before 10.0.9 Patch 2 contains a cross-site scripting vulnerability in the Webmail component that allows a remote attacker to spoof link targets or inject HTML into a message as rendered in a victim's authenticated Webmail session by sending a crafted email whose text is already inside a link. Attackers can exploit the link auto-formatter's re-processing of already-linked text, using quote characters to break out of the href attribute and inject attacker-controlled markup to execute script in the victim's session.

Weakness: CWE-83 (Improper Neutralization of Script in Attributes in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-112356 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112356 is a medium-severity vulnerability in GFI KerioConnect, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112356 in the wild and no public exploit code.

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

## Sources

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

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