VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

autobahn: vulnerability history, versions and safety

autobahn is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 117 releases, from Dec 2020 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M2 L1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all autobahn vulnerabilities

Vulert verdict on autobahn 26.10.2 i

Updated on 23 Oct 2026

Good news: 26.10.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 26.10.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.10.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 26.10.2 — unaffected i
  • Vulnerabilities on record 5 over 5 years · 2 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 456 packages i
  • Stars 2,539 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for autobahn, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.10.2 21 Oct 2026 none MIT — Details →
26.10.1 18 Oct 2026 none MIT — Details →
26.7.1 15 Jul 2026 none MIT — Details →
26.6.2 19 Jun 2026 M1 U1 MIT Yes Details →
26.6.1 18 Jun 2026 M1 U1 MIT Yes Details →
25.12.2 15 Dec 2025 M1 U1 MIT Yes Details →
25.12.1 10 Dec 2025 M1 U1 MIT Yes Details →
25.11.1 24 Nov 2025 M1 U1 MIT Yes Details →
25.10.2 22 Oct 2025 M1 U1 MIT Yes Details →
25.10.1 20 Oct 2025 M1 U1 MIT Yes Details →
25.9.1 15 Oct 2025 M1 U1 MIT Yes Details →
24.4.2 02 Aug 2024 M1 U1 MIT Yes Details →
23.6.2 14 Jun 2023 M1 U1 MIT Yes Details →
23.6.1 04 Jun 2023 M1 U1 MIT Yes Details →
23.1.2 08 Feb 2023 M1 U1 MIT Yes Details →
23.1.1 15 Jan 2023 M1 U1 MIT Yes Details →
22.12.1 18 Dec 2022 M1 U1 MIT Yes Details →
22.7.1 02 Aug 2022 M1 U1 MIT Yes Details →
22.6.1 05 Jul 2022 M1 U1 MIT Yes Details →
22.5.1 02 Jun 2022 M1 U1 MIT Yes Details →
22.4.2 04 May 2022 M1 U1 MIT Yes Details →
22.4.1 04 May 2022 M1 U1 MIT Yes Details →
22.3.2 27 Mar 2022 M1 U1 MIT Yes Details →
22.3.1 26 Mar 2022 M1 U1 MIT Yes Details →
22.2.2 24 Feb 2022 M1 U1 MIT Yes Details →
22.2.1 23 Feb 2022 M1 U1 MIT Yes Details →
22.1.1 28 Jan 2022 M1 U1 MIT Yes Details →
21.11.1 21 Nov 2021 M1 U1 MIT Yes Details →
21.3.1 02 Mar 2021 M1 U1 MIT Yes Details →
21.2.2 26 Feb 2021 M1 U1 MIT Yes Details →
21.2.1 11 Feb 2021 M1 U1 MIT Yes Details →
21.1.1 06 Feb 2021 M1 U1 MIT Yes Details →
20.12.3 19 Dec 2020 M1 U1 MIT Yes Details →
20.12.2 14 Dec 2020 M2 U2 MIT Yes Details →
20.12.1 13 Dec 2020 M2 U2 MIT Yes Details →
20.7.1 17 Jul 2020 M2 U2 MIT Yes Details →
20.6.2 29 Jun 2020 M2 U2 MIT Yes Details →
20.6.1 11 Jun 2020 M2 U2 MIT Yes Details →
20.4.3 22 Apr 2020 M2 U2 MIT Yes Details →
20.4.2 14 Apr 2020 M2 U2 MIT Yes Details →
20.4.1 31 Mar 2020 M2 U2 MIT Yes Details →
20.3.1 03 Mar 2020 M2 U2 MIT Yes Details →
20.2.2 25 Feb 2020 M2 U2 MIT Yes Details →
20.2.1 07 Feb 2020 M2 U2 MIT Yes Details →
20.1.3 24 Jan 2020 M2 U2 MIT Yes Details →
20.1.2 14 Jan 2020 M2 U2 MIT Yes Details →
19.11.2 09 Jan 2020 M2 U2 MIT Yes Details →
19.11.1 07 Nov 2019 M2 U2 MIT Yes Details →
19.10.1 30 Sep 2019 M2 U2 MIT Yes Details →
19.9.3 09 Sep 2019 M2 U2 MIT Yes Details →
19.9.2 29 Aug 2019 M2 U2 MIT Yes Details →
19.9.1 28 Aug 2019 M2 U2 MIT Yes Details →
19.8.1 01 Aug 2019 M2 U2 MIT Yes Details →
19.7.2 24 Jul 2019 M2 U2 MIT Yes Details →
19.7.1 08 Jul 2019 M2 U2 MIT Yes Details →
19.6.2 06 Jun 2019 M2 U2 MIT Yes Details →
19.6.1 05 Jun 2019 M2 U2 MIT Yes Details →
19.5.1 12 May 2019 M2 U2 MIT Yes Details →
19.3.3 24 Mar 2019 M2 U2 MIT Yes Details →
19.3.2 18 Mar 2019 M2 U2 MIT Yes Details →
19.3.1 18 Mar 2019 M2 U2 MIT Yes Details →
19.2.1 14 Feb 2019 M2 U2 MIT Yes Details →
19.1.1 10 Jan 2019 M2 U2 MIT Yes Details →
18.12.1 17 Dec 2018 M2 U2 MIT Yes Details →
18.11.2 22 Nov 2018 M2 U2 MIT Yes Details →
18.11.1 06 Nov 2018 M2 U2 MIT Yes Details →
18.10.1 20 Oct 2018 M2 U2 MIT Yes Details →
18.9.2 10 Sep 2018 M2 U2 MIT Yes Details →
18.9.1 02 Sep 2018 M2 U2 MIT Yes Details →
18.8.2 31 Aug 2018 M2 U2 MIT Yes Details →
18.8.1 19 Aug 2018 M2 U2 MIT Yes Details →
18.7.1 28 Jul 2018 M2 U2 MIT Yes Details →
18.6.1 07 Jun 2018 M2 U2 MIT Yes Details →
18.5.2 26 May 2018 M2 U2 MIT Yes Details →
18.5.1 09 May 2018 M2 U2 MIT Yes Details →
18.4.1 09 Apr 2018 M2 U2 MIT Yes Details →
18.3.1 05 Mar 2018 M2 U2 MIT Yes Details →
17.10.1 31 Oct 2017 M2 U2 MIT Yes Details →
17.9.3 24 Sep 2017 M2 U2 MIT Yes Details →
17.9.2 12 Sep 2017 M2 U2 MIT Yes Details →
17.9.1 04 Sep 2017 M2 U2 MIT Yes Details →
17.8.1 15 Aug 2017 M2 U2 MIT Yes Details →
17.7.1 21 Jul 2017 M2 U2 MIT Yes Details →
17.6.2 24 Jun 2017 M2 U2 MIT Yes Details →
17.6.1 08 Jun 2017 M2 U2 MIT Yes Details →
17.5.1 01 May 2017 M2 U2 MIT Yes Details →
0.18.2 15 Apr 2017 M2 U2 MIT Yes Details →
0.18.1 28 Mar 2017 M2 U2 MIT Yes Details →
0.18.0 26 Mar 2017 M2 U2 MIT Yes Details →
0.17.2 25 Feb 2017 M2 U2 MIT Yes Details →
0.17.1 29 Dec 2016 M2 U2 MIT Yes Details →
0.17.0 30 Nov 2016 M2 U2 MIT Yes Details →
0.16.1 07 Nov 2016 M2 U2 MIT Yes Details →
0.16.0 14 Aug 2016 M2 U2 MIT Yes Details →
0.15.0 19 Jul 2016 M2 U2 MIT Yes Details →
0.14.1 26 May 2016 M2 U2 MIT Yes Details →
0.14.0 01 May 2016 M2 U2 MIT Yes Details →
0.13.1 09 Apr 2016 M2 U2 MIT Yes Details →
0.13.0 15 Mar 2016 M2 U2 MIT Yes Details →
0.12.1 30 Jan 2016 M2 U2 MIT Yes Details →
0.11.0 09 Dec 2015 M2 U2 — Yes Details →
0.10.9 15 Sep 2015 M2 U2 — Yes Details →
0.10.8 13 Sep 2015 M2 U2 — Yes Details →
0.10.7 06 Sep 2015 M2 U2 — Yes Details →
0.10.6 05 Sep 2015 M2 U2 — Yes Details →
0.10.5.post2 09 Aug 2015 M2 U2 — Yes Details →
0.10.5 06 Aug 2015 M2 U2 — Yes Details →
0.10.4 08 May 2015 M2 U2 — Yes Details →
0.10.3 14 Apr 2015 M2 U2 — Yes Details →
0.10.2 19 Mar 2015 M2 U2 — Yes Details →
0.10.1 01 Mar 2015 M2 U2 — Yes Details →
0.10.0 19 Feb 2015 M2 U2 — Yes Details →
0.9.6 13 Feb 2015 M2 U2 — Yes Details →
0.9.5 11 Jan 2015 M2 U2 — Yes Details →
0.9.4.post2 16 Dec 2014 M2 U2 — Yes Details →
0.9.4 15 Dec 2014 M2 U2 — Yes Details →
0.9.3.post3 15 Nov 2014 M2 U2 — Yes Details →
0.9.3.post2 15 Nov 2014 M2 U2 — Yes Details →
0.9.3 10 Nov 2014 M2 U2 — Yes Details →
0.9.2 17 Oct 2014 M2 U2 — Yes Details →

The newest 120 of 195 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for autobahn

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35678: Open Redirect in autobahn 6.1 medium 20.12.3 20 Apr 2021
CVE-2026-77528: Autobahn Python permessage-deflate Bypass of maxMessagePayloadSize After Inflation 5.3 medium 26.7.1 22 Sep 2026
CVE-2026-77528: Autobahn Python permessage-deflate Bypass of maxMessagePayloadSize After Inflation 5.3 medium 26.7.1 01 Oct 2026
CVE-2020-35678: Redirect Header Injection in Autobahn|Python N/A unrated 20.12.3 27 Dec 2020
Timing attack in Autobahn N/A low 0.6.4 24 Feb 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About autobahn

Is autobahn safe to use?

Vulert records 5 vulnerabilities for autobahn in PyPI: 0 critical, 0 high, 2 medium and 1 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is autobahn's Vulert package health score?

Vulert scores autobahn 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of autobahn affected?

No. 26.10.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does autobahn have?

5 vulnerabilities are recorded for autobahn in the PyPI ecosystem: 0 critical, 0 high, 2 medium and 1 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new autobahn vulnerabilities disclosed?

2 vulnerabilities were recorded for autobahn in the last 12 months, and the oldest entry in this database dates to 27 Dec 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of autobahn are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor autobahn for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the autobahn version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.