Skip to content
WatchlistCritical

CVE-2003-1083Monit Vulnerability

Stack-based buffer overflow in Monit 1.4 to 4.1 allows remote attackers to execute arbitrary code via a long HTTP request.

Published Dec 31, 2003 · Updated Aug 4, 2026 · Also known as DEBIAN-CVE-2003-1083

Key Facts

Patch immediately
  • CVE-2003-1083 is a critical-severity vulnerability (CVSS 10.0 v2) affecting Monit (Tildeslash).
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 21% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Monit 1:4.2.1-1.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v2

10.0

AV:N/AC:L/Au:N/C:C/I:C/A:C

EPSS (30-day exploit likelihood)

21%

Higher than 97.5% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

41/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

1

Reports of active use

Advisories And Exploit References

Description

Stack-based buffer overflow in Monit 1.4 to 4.1 allows remote attackers to execute arbitrary code via a long HTTP request.

Affected Products

28 affected entries in total
ProductAffected versionsFixed in
MonitTildeslash1.4, 1.4.1, 2.0, 2.1, 2.1.1, 2.2, 2.2.1, 2.31:4.2.1-1

Patched Releases

Monit

1:4.2.1-1

Timeline

  1. Publicly disclosed

    Dec 31, 2003

  2. Last updated

    Aug 4, 2026

References

5 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2003-1083 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.