# CVE-2026-36228: Memory corruption in n/a

> A remote attacker can execute arbitrary code and read sensitive data via a buffer overflow in the chat message functionality of Easy Chat Server.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-jh5j-c5cw-c6g9

## What is CVE-2026-36228?

CVE-2026-36228 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in Easy Chat Server 3.1 allows a remote attacker to obtain sensitive information and execute arbitrary code via the chat message functionality

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2026-36228 being exploited?

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

Public exploit code:

- https://github.com/NullByte8080/CVE-2026-36228 (github_poc): https://github.com/NullByte8080/CVE-2026-36228

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36228 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-36228 in the wild and no public exploit code.

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

## Sources

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

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