Security Information

Debian takes security very seriously. We handle all security problems brought to our attention and ensure that they are corrected within a reasonable timeframe. Many advisories are coordinated with other free software vendors and are published the same day a vulnerability is made public and we also have a Security Audit team that reviews the archive looking for new or unfixed security bugs.

Experience has shown that security through obscurity does not work. Public disclosure allows for more rapid and better solutions to security problems. In that vein, this page addresses Debian's status with respect to various known security holes, which could potentially affect Debian.

Debian also participates in security standardization efforts: the Debian Security Advisories are CVE-Compatible (review the cross references) and Debian is represented in the Board of the Open Vulnerability Assessment Language project.

Keeping your Debian system secure

In order to receive the latest Debian security advisories, subscribe to the debian-security-announce mailing list.

You can use apt to easily get the latest security updates. This requires a line such as

deb http://security.debian.org/ stretch/updates main contrib non-free

in your /etc/apt/sources.list file. Then execute apt-get update && apt-get upgrade to download and apply the pending updates. The security archive is signed with the normal Debian archive signing keys.

For more information about security issues in Debian, please refer to the Security Team FAQ and a manual called Securing Debian.

Recent Advisories

These web pages include a condensed archive of security advisories posted to the debian-security-announce list.

[22 Jun 2017] DSA-3896 apache2 security update
[22 Jun 2017] DSA-3895 flatpak security update
[22 Jun 2017] DSA-3894 graphite2 security update
[22 Jun 2017] DSA-3893 jython security update
[22 Jun 2017] DSA-3892 tomcat7 security update
[22 Jun 2017] DSA-3891 tomcat8 security update
[21 Jun 2017] DSA-3890 spip security update
[19 Jun 2017] DSA-3889 libffi security update
[19 Jun 2017] DSA-3888 exim4 security update
[19 Jun 2017] DSA-3887 glibc security update
[19 Jun 2017] DSA-3886 linux security update
[18 Jun 2017] DSA-3885 irssi security update
[16 Jun 2017] DSA-3884 gnutls28 security update
[15 Jun 2017] DSA-3883 rt-authen-externalauth security update
[15 Jun 2017] DSA-3882 request-tracker4 security update
[14 Jun 2017] DSA-3881 firefox-esr security update
[14 Jun 2017] DSA-3880 libgcrypt20 security update
[13 Jun 2017] DSA-3879 libosip2 security update
[12 Jun 2017] DSA-3878 zziplib security update
[10 Jun 2017] DSA-3877 tor security update
[09 Jun 2017] DSA-3876 otrs2 security update
[09 Jun 2017] DSA-3875 libmwaw security update
[09 Jun 2017] DSA-3874 ettercap security update
[05 Jun 2017] DSA-3873 perl security update
[01 Jun 2017] DSA-3872 nss security update
[01 Jun 2017] DSA-3871 zookeeper security update
[01 Jun 2017] DSA-3870 wordpress security update
[01 Jun 2017] DSA-3869 tnef security update
[30 May 2017] DSA-3868 openldap security update
[30 May 2017] DSA-3867 sudo security update
[30 May 2017] DSA-3866 strongswan security update
[29 May 2017] DSA-3865 mosquitto security update
[27 May 2017] DSA-3864 fop security update
[25 May 2017] DSA-3863 imagemagick security update
[25 May 2017] DSA-3862 puppet security update
[24 May 2017] DSA-3861 libtasn1-6 security update
[24 May 2017] DSA-3860 samba security update

The latest Debian security advisories are also available in RDF format. We also offer a second file that includes the first paragraph of the corresponding advisory so you can see in it what the advisory is about.

The older security advisories are also available: 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 1999, 1998, 1997 and undated security advisories, included for posterity.

Debian distributions are not vulnerable to all security problems. The Debian Security Tracker collects all information about the vulnerability status of Debian packages, and can be searched by CVE name or by package.

Contact Information

Please read the Security Team FAQ before contacting us, your question may well be answered there already!

The contact information is in the FAQ as well.