Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-51055: Insecure Data Storage of credentials has been found in /api_vedo/configuration/config.yml file in Vedo Suite v

46
This week
HIGH 8.6REMOTEDOWNGRADE

CVE-2025-51055 is a high-severity flaw (CVSS 8.6) affecting vedo suite. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Insecure Data Storage of credentials has been found in /api_vedo/configuration/config.yml file in Vedo Suite version 2024.17. This file contains clear-text credentials, secret keys, and database information.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 75%)
CISA exploited listNo
WeaknessCWE-312
Published2025-08-06
Last modified2026-07-05
Publisher (CNA): MITRE · Vendor: vedo suite project

Share: LinkedIn · X · Reddit

Last updated 2026-07-05 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vedo suite project vedo suite DOWNGRADE
Affected: 2024.17
Fixed in: no fixed release known
Safe to downgrade to: a release before 2024.17
1. Check installed version
apt-cache policy vedo-suite || rpm -q vedo-suite || vedo-suite --version
2. No fixed release: DOWNGRADE to a release before 2024.17 (Debian / Ubuntu)
apt-cache madison vedo-suite sudo apt install vedo-suite=<VERSION_BEFORE_2024.17> sudo apt-mark hold vedo-suite
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list vedo-suite sudo dnf downgrade vedo-suite-<VERSION_BEFORE_2024.17> sudo dnf versionlock add vedo-suite
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-51055?

vedo suite: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-51055 being exploited?

CVE-2025-51055 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-51055 affect?

CVE-2025-51055 affects vedo suite. Severity is high (CVSS 8.6). Insecure Data Storage of credentials has been found in /api_vedo/configuration/config.yml file in Vedo Suite version 2024.17. This file contains clear-text credentials, secret keys, and database information.

How urgent is CVE-2025-51055?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.