# CVE-2023-54330: Inbit Messenger 4.9.0 - Unauthenticated Remote SEH Overflow

> Unauthenticated attackers can execute arbitrary code on Windows systems by sending malformed network packets to Inbit Messenger.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-hj52-rqmp-xwx6

## What is CVE-2023-54330?

CVE-2023-54330 is a critical memory corruption vulnerability in Inbit Messenger, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inbit Messenger versions 4.6.0 to 4.9.0 contain a remote stack-based buffer overflow vulnerability that allows unauthenticated attackers to execute arbitrary code by sending malformed network packets. Attackers can craft a specially designed payload targeting the messenger's network handler to overwrite the Structured Exception Handler (SEH) and execute shellcode on vulnerable Windows systems.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-54330?

It affects 1 product.


Products: Inbit Inbit Messenger.

## How do I fix CVE-2023-54330?

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

## Is CVE-2023-54330 being exploited?

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

## Other vulnerabilities in Inbit Messenger

- [CVE-2023-54329](https://insights.sbomify.com/CVE-2023-54329/): Inbit Messenger 4.9.0 - Unauthenticated Remote Command Execution (RCE) (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54330 and fix it if it is affected.

What it is: CVE-2023-54330 is a critical memory corruption vulnerability in Inbit Messenger, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-54330 exists.

Affected product: Inbit Messenger. 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-2023-54330/ (Markdown: https://insights.sbomify.com/CVE-2023-54330/index.md)
```

## Sources

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

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