# CVE-2023-46273: Memory corruption in IQ Engine

> A buffer overflow in the Bonjour Gateway allows attackers to execute arbitrary code or cause a denial of service on Extreme Networks IQ Engine.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-4vmj-722q-82r2

## What is CVE-2023-46273?

CVE-2023-46273 is a high-severity memory corruption vulnerability in extremenetworks IQ Engine, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bonjour Gateway in Extreme Networks IQ Engine before 10.6r1a, and through 10.6r4 before 10.6r5, has an ah_bgd buffer overflow via ah_event_send.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2023-46273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46273 is a high-severity memory corruption vulnerability in extremenetworks IQ Engine, published on 14 Sep 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-2023-46273 in the wild and no public exploit code.

Affected product: extremenetworks IQ Engine. 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-46273/ (Markdown: https://insights.sbomify.com/CVE-2023-46273/index.md)
```

## Sources

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

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