Vulert records 2 vulnerabilities for ctn in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does ctn have?

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

0 vulnerabilities were recorded for ctn in the last 12 months, and the oldest entry in this database dates to 18 Nov 2008. 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 ctn 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 ctn for upcoming vulnerabilities?

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

Vulnerability Database · Debian · Package report

ctn: vulnerability history, versions and safety

ctn is a package in the Debian ecosystem. Vulert records 2 vulnerabilities for it across 4 releases, first recorded in Nov 2008. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded U2

2 with no fix published

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

See the unfixed vulnerabilities →

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ctn vulnerabilities

Vulert verdict on ctn i

Updated on 23 Oct 2026

Careful: 2 of the 2 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

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

What to do: Plan around the 2 vulnerabilities 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 2 over 1 year · 0 in the last year i
Latest disclosure 18 Nov 2008 i
Highest CVSS n/a i
With no published fix 2 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert holds for ctn, 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.

Version	Vulert vulnerabilities	Fix published	Details
3.2.0~dfsg-9	U1	No	Details →
3.2.0~dfsg-8	U2	No	Details →
3.2.0~dfsg-7.1	U2	No	Details →
3.2.0~dfsg-7	U2	No	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2008 2

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for ctn

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Symlink Attack in ctn Package	N/A unrated	No fix published	18 Nov 2008
Symlink Vulnerability in ctn Package Allows Local File Overwrite	N/A unrated	No fix published	18 Nov 2008

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