dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2026-44516

HIGH · 7.6 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LoggingRestClientCustomizer in Valtimo's web module intercepts all outgoing HTTP calls made via Spring's RestClient and logs full request bodies, response bodies, and response headers. When HTTP errors occur, this sensitive data is included in HttpClientErrorException messages that Spring logs at ERROR level regardless of the application's DEBUG log level setting, causing unintended information disclosure.

MitigationUpgrade to Valtimo version 12.33.0, 13.26.0, or later where the LoggingRestClientCustomizer no longer includes sensitive HTTP body and header data in logged exceptions. Alternatively, audit logging configurations and disable or customize the customizer to prevent sensitive data leakage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Valtimo deployment
    Identify if the Valtimo application is deployed by checking for valtimo-related JAR files, dependencies, or the valtimo web module in the classpath/application
    Affected if Valtimo is present in the environment
  2. Check Valtimo version
    Locate the Valtimo version in build files (pom.xml, build.gradle), WAR file manifest, or application metadata; compare against the fixed versions 12.33.0 and 13.26.0
    Affected if The installed version is earlier than 12.33.0 or 13.26.0 (pre-fix versions)
  3. Identify LoggingRestClientCustomizer presence
    Search for the class LoggingRestClientCustomizer in the application codebase or JAR files within the valtimo-web module; check if it is registered as a Spring bean in configuration
    Affected if LoggingRestClientCustomizer class exists and is loaded as a bean in the Spring context
  4. Verify RestClient usage
    Check if the application uses Spring's RestClient for outgoing HTTP calls, as the customizer only intercepts RestClient-based requests
    Affected if The application makes HTTP calls via RestClient that would be intercepted by the customizer
  5. Inspect logging configuration
    Review logging configuration files (logback.xml, log4j.properties, application.yml) for ERROR-level logging handlers that may capture HttpClientErrorException messages containing request/response bodies
    Affected if ERROR-level logging is enabled and would capture exceptions thrown by the customizer

A user is affected if Valtimo with a version earlier than 12.33.0 or 13.26.0 is deployed, the LoggingRestClientCustomizer is active in the Spring context, and the application uses RestClient for HTTP calls with sensitive data in request or response bodies.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Valtimo version 12.33.0, 13.26.0, or later where the LoggingRestClientCustomizer no longer includes sensitive HTTP body and header data in logged exceptions. Alternatively, audit logging configurations and disable or customize the customizer to prevent sensitive data leakage.

Recommended fix High confidence

12.33.0 or 13.26.0 (depending on major version branch in use)

  1. 1. Identify the current Valtimo version in use by checking the project's dependency management (e.g., pom.xml, build.gradle, or application properties)
  2. 2. If using version 12.x: upgrade to version 12.33.0 or later
  3. 3. If using version 13.x: upgrade to version 13.26.0 or later
  4. 4. Verify the upgrade by rebuilding the project and running existing test suites
  5. 5. Confirm that LoggingRestClientCustomizer no longer logs sensitive HTTP body and header data at ERROR level
Caveat Review release notes for any breaking changes between current version and target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44516 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data