VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

twisted: vulnerability history, versions and safety

twisted is a package in the Debian ecosystem. Vulert records 28 vulnerabilities for it across 27 releases, from Jun 2019 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded U28
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 11 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all twisted vulnerabilities

Vulert verdict on twisted i

Updated on 23 Oct 2026

Careful: one of the 28 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 28 vulnerabilities on record across 6 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 28 over 6 years · 1 in the last year i
  • Latest disclosure 11 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i

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 holds for twisted, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 27 of 27 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 6
  • 2020 6
  • 2022 8
  • 2023 2
  • 2024 5
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for twisted

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
HTTP Request Splitting Vulnerability in Twisted Package 9.8 critical 18.9.0-7 12 Mar 2020
Critical HTTP Request Splitting Vulnerability in Twisted Web 9.8 critical 18.9.0-7 12 Mar 2020
HTTP Request Smuggling Vulnerability in Twisted Package 8.1 high 20.3.0-7+deb11u1 04 Apr 2022
Memory Exhaustion Vulnerability in Twisted SSH Implementation 7.5 high 20.3.0-7+deb11u1 03 Mar 2022
Critical TrustRoot Bypass in Twisted Package: CVE-2014-7143 7.5 high 14.0.2-1 12 Nov 2019

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 twisted

Is twisted safe to use?

Vulert records 28 vulnerabilities for twisted in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 28 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does twisted have?

28 vulnerabilities are recorded for twisted in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 28 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 twisted vulnerabilities disclosed?

1 vulnerability was recorded for twisted in the last 12 months, and the oldest entry in this database dates to 10 Jun 2019. 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 twisted 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 twisted for upcoming vulnerabilities?

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