VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

kde4libs: vulnerability history, versions and safety

kde4libs is a package in the Debian ecosystem. Vulert records 12 vulnerabilities for it across 3 releases, from May 2009 to Feb 2014. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded U12
i
5 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all kde4libs vulnerabilities

Vulert verdict on kde4libs i

Updated on 23 Oct 2026

Careful: 5 of the 12 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

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

What to do: Plan around the 5 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 12 over 4 years · 0 in the last year i
  • Latest disclosure 05 Feb 2014 i
  • Highest CVSS n/a i
  • With no published fix 5 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 kde4libs, 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.

i
Version Vulert vulnerabilities Fix published Details
4:4.14.38-4 U5 No Details →
4:4.14.38-4~exp1 U5 No Details →
4:4.14.38-3 U5 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 9
  • 2011 2
  • 2014 1

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

03 Vulnerabilities

Recorded vulnerabilities for kde4libs

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2011-1094: KDE KSSL Spoofing Vulnerability in kde4libs N/A unrated 4:4.4.5-4 16 Mar 2011
Cross-Site Scripting (XSS) in QtWeb 3.0 Builds 001 and 003 N/A unrated No fix published 31 Aug 2009
Stack Consumption Vulnerability in WebKit.dll in Apple Safari N/A unrated No fix published 21 Sep 2009
CVE-2009-2702: KDE KSSL Spoofing Vulnerability in kdelibs N/A unrated 4:4.3.2-1 08 Sep 2009
Cross-site scripting (XSS) vulnerability in Konqueror in KDE SC 4.4.0 through 4.6.1 N/A unrated 4:4.4.5-4 18 Apr 2011

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 kde4libs

Is kde4libs safe to use?

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

How many vulnerabilities does kde4libs have?

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

0 vulnerabilities were recorded for kde4libs in the last 12 months, and the oldest entry in this database dates to 13 May 2009. 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 kde4libs 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 kde4libs for upcoming vulnerabilities?

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