dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-40137

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
SAP TAF_APPLAUNCHER within Business Server Pages allows an unauthenticated attacker to craft malicious links that, when clicked by a victim, redirects them to attacker?controlled sites, potentially exposing or altering sensitive information in the victim�s browser. This results in a low impact on confidentiality and integrity, with no impact on the availability of the application.

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

This is an open redirect vulnerability in SAP TAF_APPLAUNCHER within Business Server Pages. Unauthenticated attackers can craft malicious URLs containing attacker-controlled redirect targets that, when clicked by victims, redirect them to malicious sites, potentially enabling phishing attacks or browser-based information exposure.

MitigationImplement strict URL validation and whitelist-based redirect controls in the TAF_APPLAUNCHER to ensure only trusted, internal domains are allowed as redirect targets.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify TAF_APPLAUNCHER component presence
    Access SAP system administration and check if the TAF_APPLAUNCHER component is installed or deployed. In SAP transactions, use SE11 or SE80 to search for TAF_APPLAUNCHER-related objects in the BSP application namespace.
    Affected if TAF_APPLAUNCHER component is found installed in the SAP environment
  2. Identify Business Server Pages framework
    Use SAP transaction code SE80 or SE61 to browse BSP applications. Look for applications containing 'TAF_APPLAUNCHER' in the application name or namespace.
    Affected if BSP application named TAF_APPLAUNCHER exists in the system
  3. Inspect redirect parameter handling
    Access the TAF_APPLAUNCHER BSP application source code (using SE80) and examine the logic that handles redirect parameters, typically in the controller or handler class. Look for code that processes 'redirect', 'url', 'target', or similar parameters.
    Affected if Code accepts redirect parameters without strict validation against a whitelist of trusted domains
  4. Check URL validation configuration
    Review any custom validation logic or configuration tables that define allowed redirect targets. Use transaction code SE16 to inspect custom tables related to URL allowlists or redirect validation.
    Affected if No strict allowlist-based URL validation is configured, or the validation logic is missing entirely
  5. Determine SAP system version range
    Execute SAP transaction SM37 or use ABAP to call function module 'SWN_CONFIG_GET' or check system version via transaction S001/S001 to obtain the SAP BASIS version. Compare against any applicable version ranges for this vulnerability.
    Affected if Running an SAP BASIS version that falls within an affected version range for this open redirect flaw

The environment is affected if the TAF_APPLAUNCHER BSP component is present and the redirect handling logic does not enforce strict allowlist-based URL validation before performing redirects.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and whitelist-based redirect controls in the TAF_APPLAUNCHER to ensure only trusted, internal domains are allowed as redirect targets.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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