Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for n/a/n/a.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Jul 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 3, 2026

Sources and claim methodology

• Source referencecudy.com

Related CVEs

• Langflow is affected by weaknesses in secret handling and sensitive configuration accessSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcementSame generic ecosystem
• Denial of service vulnerability in GitHub Enterprise Server allowed unauthenticated service disruption via deeply nested request parametersSame generic ecosystem
• Path traversal in GitHub Enterprise Server allowed unauthenticated deletion of instance storage via the X-GitHub-Request-Id headerSame generic ecosystem
• Thermo Fisher Applied Biosystems Genetic Analyzers Missing Support for Integrity CheckSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handlingSame generic ecosystem

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for n/a/n/a.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Jul 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 3, 2026

Sources and claim methodology

• Source referencecudy.com

Related CVEs

• Langflow is affected by weaknesses in secret handling and sensitive configuration accessSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcementSame generic ecosystem
• Denial of service vulnerability in GitHub Enterprise Server allowed unauthenticated service disruption via deeply nested request parametersSame generic ecosystem
• Path traversal in GitHub Enterprise Server allowed unauthenticated deletion of instance storage via the X-GitHub-Request-Id headerSame generic ecosystem
• Thermo Fisher Applied Biosystems Genetic Analyzers Missing Support for Integrity CheckSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handlingSame generic ecosystem