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.
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/debian-security stretch/updates main contrib non-free
/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
These web pages include a condensed archive of security advisories posted to the debian-security-announce list.
[17 Nov 2017] DSA-4040 imagemagick security update
[16 Nov 2017] DSA-4039 opensaml2 security update
[16 Nov 2017] DSA-4038 shibboleth-sp2 security update
[16 Nov 2017] DSA-4037 jackson-databind security update
[15 Nov 2017] DSA-4036 mediawiki security update
[15 Nov 2017] DSA-4035 firefox-esr security update
[15 Nov 2017] DSA-4034 varnish security update
[13 Nov 2017] DSA-4033 konversation security update
[12 Nov 2017] DSA-4032 imagemagick security update
[11 Nov 2017] DSA-4031 ruby2.3 security update
[09 Nov 2017] DSA-4030 roundcube security update
[09 Nov 2017] DSA-4029 postgresql-common security update
[09 Nov 2017] DSA-4028 postgresql-9.6 security update
[09 Nov 2017] DSA-4027 postgresql-9.4 security update
[09 Nov 2017] DSA-4026 bchunk security update
[08 Nov 2017] DSA-4025 libpam4j security update
[08 Nov 2017] DSA-4024 chromium-browser security update
[07 Nov 2017] DSA-4023 slurm-llnl security update
[07 Nov 2017] DSA-4022 libreoffice security update
[07 Nov 2017] DSA-4021 otrs2 security update
[05 Nov 2017] DSA-4020 chromium-browser security update
[05 Nov 2017] DSA-4019 imagemagick security update
[04 Nov 2017] DSA-4018 openssl security update
[03 Nov 2017] DSA-4017 openssl1.0 security update
[03 Nov 2017] DSA-4016 irssi security update
[02 Nov 2017] DSA-4015 openjdk-8 security update
[01 Nov 2017] DSA-4014 thunderbird security update
[31 Oct 2017] DSA-4013 openjpeg2 security update
[31 Oct 2017] DSA-4012 libav security update
[30 Oct 2017] DSA-4011 quagga security update
[30 Oct 2017] DSA-4010 git-annex security update
[29 Oct 2017] DSA-4009 shadowsocks-libev security update
[28 Oct 2017] DSA-4008 wget security update
[27 Oct 2017] DSA-4007 curl security update
[24 Oct 2017] DSA-4006 mupdf security update
[20 Oct 2017] DSA-4005 openjfx security update
[20 Oct 2017] DSA-4004 jackson-databind security update
[19 Oct 2017] DSA-4003 libvirt security update
[19 Oct 2017] DSA-4002 mysql-5.5 security update
[19 Oct 2017] DSA-4001 yadifa 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.
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.