# CVE-2026-3697: Planet ICG-2510 Language Package Configuration httpd sub_40C8E4 stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the Planet ICG-2510 httpd service via the Language argument, potentially leading to code execution or service disruption.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 8 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-hff3-38mc-m39m

## What is CVE-2026-3697?

CVE-2026-3697 is a medium-severity memory corruption vulnerability in Planet ICG-2510, published on 8 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Planet ICG-2510 1.0_20250811. The impacted element is the function sub_40C8E4 of the file /usr/sbin/httpd of the component Language Package Configuration Handler. Executing a manipulation of the argument Language can lead to stack-based buffer overflow. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-3697 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3697 is a medium-severity memory corruption vulnerability in Planet ICG-2510, published on 8 Mar 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-3697 in the wild and no public exploit code.

Affected product: Planet ICG-2510. 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-3697/ (Markdown: https://insights.sbomify.com/CVE-2026-3697/index.md)
```

## Sources

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

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