# CVE-2026-116583: Seroval: Code injection through a typed array's own constructor property


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-f86p-h4j2-7qgj

## What is CVE-2026-116583?

CVE-2026-116583 is a medium-severity vulnerability in lxsmnsyc seroval, published on 26 Oct 2026. 

### Official description

Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. From 1.6.0 until 1.6.11, the JavaScript-output APIs derive a typed array's constructor name from a property on the value that can be replaced by an own constructor property. When application code copies untrusted properties onto a typed array and then passes it to serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, Serializer, or compileJSON, the attacker-controlled name is written as executable JavaScript and can run in the page receiving the output. This issue is fixed in version 1.6.11.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including seroval.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `seroval` | npm | From 1.6.0 | 1.6.11 |
| `seroval` | npm | From 1.6.0 | 1.6.11 |

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

Upgrade seroval to 1.6.11 or later.

## Is CVE-2026-116583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116583 is a medium-severity vulnerability in lxsmnsyc seroval, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116583 in the wild and no public exploit code.

Affected packages and fixed versions:
- seroval (npm): affected from 1.6.0; fixed in 1.6.11
- seroval (npm): affected from 1.6.0; fixed in 1.6.11

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-116583/ (Markdown: https://insights.sbomify.com/CVE-2026-116583/index.md)
```

## Sources

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

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