VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

socat: vulnerability history, versions and safety

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

i
15 vulnerabilities recorded U15
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 25 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all socat vulnerabilities

Vulert verdict on socat i

Updated on 23 Oct 2026

Careful: one of the 15 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 15 vulnerabilities on record across 21 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 15 over 21 years · 1 in the last year i
  • Latest disclosure 25 Jun 2026 i
  • Highest CVSS 7.5 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 socat, 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

  • 2004 2
  • 2010 2
  • 2012 2
  • 2014 4
  • 2017 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for socat

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in socat - CVE-2015-1379 7.5 high 1.7.2.4-2 08 Jun 2017
Insecure DH Implementation in Socat: CVE-2016-2217 Vulnerability 5.3 medium 1.7.3.1-1 30 Jan 2017
Denial of Service Vulnerability in socat Package: CVE-2013-3571 N/A unrated 1.7.1.3-1.5 08 May 2014
Buffer Overflow Vulnerability in Socat Package: CVE-2014-0019 N/A unrated 1.7.2.3-1 04 Feb 2014
Heap-Based Buffer Overflow in Socat: CVE-2012-0219 N/A unrated 1.7.1.3-1.3 21 Jun 2012

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 socat

Is socat safe to use?

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

How many vulnerabilities does socat have?

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

1 vulnerability was recorded for socat in the last 12 months, and the oldest entry in this database dates to 31 Dec 2004. 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 socat 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 socat for upcoming vulnerabilities?

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