Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-7657: IBM Langflow OSS 1.0.0 through 1.10.3 Langflow could allow server-side request forgery (SSRF) due to incomplet

30
Routine
MEDIUM 6.5UPGRADE

CVE-2026-7657 is a medium-severity flaw (CVSS 6.5) affecting langflow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Langflow OSS 1.0.0 through 1.10.3 Langflow could allow server-side request forgery (SSRF) due to incomplete and ineffective SSRF protection enforcement.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 70%)
CISA exploited listNo
WeaknessCWE-918
Published2026-08-05
Last modified2026-10-23
Publisher (CNA): IBM Corporation · Vendor: langflow

Am I affected?

Timeline

langflow langflow UPGRADE
Affected: >= 1.0.0 and < 1.11.0
Fixed in: 1.11.0
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy langflow || rpm -q langflow || langflow --version
2. UPGRADE to 1.11.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade langflow
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade langflow
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison langflow sudo apt install langflow=<VERSION_BEFORE_1.0.0> sudo apt-mark hold langflow
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list langflow sudo dnf downgrade langflow-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add langflow
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.

Related CVEs

References

← Back to latest CVEs