Quick answers
- Is CVE-2026-33497 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33497 being exploited in the wild.
- How severe is CVE-2026-33497?
- High severity, with a CVSS score of 4, published 20 March 2026.
- Which products and versions are affected?
- Langflow < 1.7.1; langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.7.1.
- Is there a fix for CVE-2026-33497?
- Yes. langflow (PyPI): upgrade to 1.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33497 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-33497?
- Check whether you run Langflow or langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langflow (PyPI): upgrade to 1.7.1 or later
pip install "langflow>=1.7.1"
Technical details
A path traversal vulnerability exists in the `download_profile_picture` function within `src/backend/base/langflow/api/v1/files.py`. The application fails to sanitize the `folder_name` and `file_name` path parameters before concatenating them to a base directory path. An unauthenticated attacker can use `../` sequences to escape the intended directory and read arbitrary files, such as the `secret_key` file used for JWT signing. This exfiltration enables the forgery of administrative tokens. The issue is fixed in version 1.7.1 by implementing typed path validation and strict path containment checks using `Path.is_relative_to()`.
Affected products
- langflow-ai langflow < 1.7.1
Identifiers
- CVE-2026-33497
- GHSA-ph9w-r52h-28p7
- PYSEC-2026-81
Timeline
- 2026-03-20: disclosed
- 2026-03-20: advisory
- 2026-03-20: patched: Fixed in version 1.7.1