NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2023-25392 — bigflow

MEDIUMFix: allegro/bigflow#357

CVE-2023-25392 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in bigflow. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for bigflow — see the affected versions and patch details below.

Allegro Tech BigFlow vulnerable to Missing SSL Certificate Validation

Also known asGHSA-w6q2-48ch-fj26PYSEC-2026-1220
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-25392.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍bigflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Allegro Tech BigFlow prior to 1.6.0 is vulnerable to Missing SSL Certificate Validation.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIbigflowall versions1.6.0pip install --upgrade 'bigflow==1.6.0'

Affected Products

1 product · 1 configurations
Application
bigflowallegro
< 1.6
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bigflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update bigflow to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-25392 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Allegro Tech BigFlow prior to 1.6.0 is vulnerable to Missing SSL Certificate Validation.
O3 Security · Impact-Aware SCA

Is CVE-2023-25392 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2023-25392: bigflow — Fixed in 1.6.0