Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-36075IBM Safer Payments could allow an authenticated user to obtain sensitive information

Description

IBM Safer Payments 6.4.0.00 through 6.4.2.11, 6.5.0.00 through 6.5.0.09, 6.6.0.00 through 6.6.0.07, 6.7.0.00 through 6.7.0.03, and 6.8.0.00 could allow an authenticated user to obtain sensitive information, caused by improper user input validation. By using a set of API requests the user could exploit this vulnerability to decrypt sensitive information.

Timeline

  1. ID reserved

    By ibm

  2. · 19 months later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-36075, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.1Medium5.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Awaiting Analysis3.1Medium5.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Affected products

  • IBM · Safer Payments

    • affected 6.4.0.00 – ≤ 6.4.2.11
    • affected 6.5.0.00 – ≤ 6.5.0.09
    • affected 6.6.0.00 – ≤ 6.6.0.07
    • affected 6.7.0.00 – ≤ 6.7.0.03
    • affected 6.8.0.00

What to do

Solution: Update IBM Safer Payments to version 6.4.2.12, 6.5.0.10, 6.6.0.08, 6.7.0.04, 6.8.0.01 or higher. Refer to the IBM Safer Payments documentation https://www.ibm.com/docs/en/safer-payments  to download the updates.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-36075 badge
[![CVE-2025-36075](https://cveledger.app/badge/CVE-2025-36075.svg)](https://cveledger.app/cve/CVE-2025-36075)

Record last updated .