dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-40127

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
OutSystems Lifetime is vulnerable to Authorization Bypass Through User-Controlled Key vulnerability in ApplicationID parameter. Any authenticated user, can read the Change Log containing actions performed by other users as well as application name of any application. This issue was fixed in OutSystems Lifetime version 11.28.2.3955

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

OutSystems Lifetime contains an Insecure Direct Object Reference (IDOR) vulnerability where the ApplicationID parameter in the Change Log feature is not properly validated against the authenticated user's authorization. Any authenticated user can manipulate this parameter to read change logs and application names of applications they do not own or have access to, effectively bypassing authorization controls.

MitigationUpgrade OutSystems Lifetime to version 11.28.2.3955 or later. If immediate upgrade is not possible, implement authorization checks on the ApplicationID parameter to ensure users can only access change logs for applications they are authorized to view.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 OutSystems Lifetime installation
    Locate OutSystems installation directory or check for 'lifetime.exe' or version configuration files in typical OutSystems installation paths (e.g., C:\Program Files\OutSystems\ or /opt/OutSystems/). Alternatively, access the Lifetime Management Console and note the platform version displayed.
    Affected if The system is running OutSystems Lifetime platform.
  2. Check installed Lifetime version against fixed release
    In the Lifetime Management Console, navigate to the 'About' or 'Diagnostics' section to view the exact platform version number. Compare this version to 11.28.2.3955.
    Affected if The installed version is lower than 11.28.2.3955.
  3. Verify Change Log module is enabled
    Access the Lifetime Management Console and confirm the 'Change Log' or 'Audit' functionality is available under the Applications or Diagnostics menu. Check configuration files (e.g., Lifetime configuration XML or JSON files) for enablement status.
    Affected if The Change Log feature is present and enabled in the platform.
  4. Confirm user authentication context for Change Log access
    Log into Lifetime as a standard (non-admin) user with limited application permissions. Navigate to the Change Log section and attempt to modify the ApplicationID parameter in the request (via browser developer tools or API call) to point to an application the user does not own.
    Affected if An authenticated user can access change logs for applications they are not authorized to view by manipulating the ApplicationID parameter.

A system is affected if it runs OutSystems Lifetime version lower than 11.28.2.3955 with the Change Log feature enabled and allows unauthorized access via ApplicationID parameter manipulation.

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 OutSystems Lifetime to version 11.28.2.3955 or later. If immediate upgrade is not possible, implement authorization checks on the ApplicationID parameter to ensure users can only access change logs for applications they are authorized to view.

Recommended fix High confidence

OutSystems Lifetime version 11.28.2.3955

  1. Upgrade OutSystems Lifetime to version 11.28.2.3955 or later

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40127 — 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-40127 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