Skip to content
Emerging threatsCritical

CVE-2003-1336Mirc Memory Corruption

Buffer overflow in mIRC before 6.11 allows remote attackers to execute arbitrary code via a long irc:// URL.

Published Dec 31, 2003 · Updated Apr 15, 2026

Key Facts

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

Scores

CVSS v2

9.3

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

EPSS (30-day exploit likelihood)

36%

Higher than 98.4% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

55/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

Weaponized

Public exploit code

3

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

Buffer overflow in mIRC before 6.11 allows remote attackers to execute arbitrary code via a long irc:// URL.

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
MircMircSee advisory6.1

Patched Releases

Mirc

6.1

Timeline

  1. Publicly disclosed

    Dec 31, 2003

  2. Last updated

    Apr 15, 2026

Weakness Type

  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

4 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2003-1336 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.