# CVE-2026-116098: SteelRaven7 Ravenfield RFL Custom Map Handler/RFLD Custom Map cacheCoverPoints deserialization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-623g-5673-24x6

## What is CVE-2026-116098?

CVE-2026-116098 is a medium-severity vulnerability in SteelRaven7 Ravenfield, published on 25 Oct 2026. 

### Official description

A vulnerability was detected in SteelRaven7 Ravenfield 25407073. This vulnerability affects the function cacheCoverPoints of the component RFL Custom Map Handler/RFLD Custom Map Handler. Performing a manipulation results in deserialization. Remote exploitation of the attack is possible. The patch is named EA39 Security Patch. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Steelraven7 Ravenfield.

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

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

## Is CVE-2026-116098 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116098 is a medium-severity vulnerability in SteelRaven7 Ravenfield, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116098 in the wild and no public exploit code.

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

## Sources

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

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