# CVE-2026-44516: Valtimo: Sensitive data exposure through HTTP request/response logging in LoggingRestClientCustomizer

> Attackers with log access can view sensitive data from HTTP requests and responses logged by the Valtimo platform.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-3jh5-rr2q-xfv7

## What is CVE-2026-44516?

CVE-2026-44516 is a high-severity vulnerability in com.ritense.valtimo valtimo, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Valtimo is an open-source business process automation platform. From 12.4.0 to 12.33.0 and 13.26.0, the LoggingRestClientCustomizer in the web module automatically intercepts all outgoing HTTP calls made via Spring's RestClient and logs the full request body, response body, and response headers. When an error response is received, this information is included in the thrown HttpClientErrorException message, which is logged at ERROR level by Spring's default exception handling — regardless of the application's DEBUG log level setting. This vulnerability is fixed in 12.33.0 and 13.26.0.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

4 open source packages ship an affected version, including com.ritense.valtimo:web.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ritense.valtimo:web` | Maven | From 12.4.0 | 12.33.0 |
| `com.ritense.valtimo:web` | Maven | From 12.4.0 | 12.33.0 |
| `com.ritense.valtimo:web` | Maven | From 13.0.0 | 13.26.0 |
| `com.ritense.valtimo:web` | Maven | From 13.0.0 | 13.26.0 |

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

Upgrade com.ritense.valtimo:web to a fixed version for your release line: 12.33.0 or 13.26.0.

## Is CVE-2026-44516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44516 is a high-severity vulnerability in com.ritense.valtimo valtimo, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44516 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.ritense.valtimo:web (Maven): affected from 12.4.0; fixed in 12.33.0
- com.ritense.valtimo:web (Maven): affected from 12.4.0; fixed in 12.33.0
- com.ritense.valtimo:web (Maven): affected from 13.0.0; fixed in 13.26.0
- com.ritense.valtimo:web (Maven): affected from 13.0.0; fixed in 13.26.0

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

## Sources

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

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