Skip to content
Fencer Vulns
medium 6.8

CVE-2025-8864 json

Shared Access Signature token is not masked in the backup configuration response and is also exposed in the yb_backup logs

published 2025-08-11 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-24151

cvss
6.8
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

Shared Access Signature token is not masked in the backup configuration response and is also exposed in the yb_backup logs

Patch / fix

  • YugabyteDB Inc YugabyteDB Anywhere 2.23.1.0, 2024.1.3.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-8864 updated cvss 3.5

yugabytedb: YugabyteDB token exposure

  • Red Hat JBoss Enterprise Application Platform 8 yugabytedb Red Hat JBoss Enterprise Application Platform Expansion Pack yugabytedb
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
14 mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 6.8 CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
CNA 4.0 6.8 CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/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

Affected products

  • YugabyteDB Inc YugabyteDB Anywhere

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.