# CVE-2026-97865: Open-Web-Analytics Remote Event Queue Endpoint queue.php loadFromArray deserialization


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-j84g-3jrc-vgcr

## What is CVE-2026-97865?

CVE-2026-97865 is a medium-severity vulnerability in Open-Web-Analytics, published on 25 Sep 2026. 

### Official description

A security flaw has been discovered in Open-Web-Analytics up to 1.8.1. Affected is the function Event::loadFromArray of the file queue.php of the component Remote Event Queue Endpoint. Performing a manipulation results in deserialization. The attack can be initiated remotely. Upgrading to version 1.8.2 is able to address this issue. The patch is named 78c1222ec0e2119d84684032da1541120a2cdd23. The affected component should be upgraded.

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

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


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

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

## Is CVE-2026-97865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97865 is a medium-severity vulnerability in Open-Web-Analytics, published on 25 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-97865 in the wild and no public exploit code.

Affected product: Open-Web-Analytics. 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-97865/ (Markdown: https://insights.sbomify.com/CVE-2026-97865/index.md)
```

## Sources

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

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