# CVE-2026-91842: OpenBankProject OBP-API Kryo Redis.scala KryoInjection.invert deserialization

> Remote attackers can exploit a deserialization flaw in the Kryo Redis handler to potentially execute arbitrary code, though high complexity limits exploitability.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-v52x-hx5q-93rv

## What is CVE-2026-91842?

CVE-2026-91842 is a low-severity unsafe deserialization vulnerability in OpenBankProject OBP-API, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in OpenBankProject OBP-API up to 1.10.1. This impacts the function KryoInjection.invert of the file obp-api/src/main/scala/code/api/cache/Redis.scala of the component Kryo Handler. Such manipulation leads to deserialization. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is said to be difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-91842 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91842 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91842 is a low-severity unsafe deserialization vulnerability in OpenBankProject OBP-API, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91842 exists.

Affected product: OpenBankProject OBP-API. 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-91842/ (Markdown: https://insights.sbomify.com/CVE-2026-91842/index.md)
```

## Sources

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

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