Skip to main content
VulnerabilityPublished Updated

CVE-2026-33333: Combodo iTop · Generation of Error Message Containing Sensitive Information

Affects Combodo iTopSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.5 Low : upgrade to 3.2.3 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade iTop and combodo/iTop to 3.2.3.

Affected software

ProductAffectedFixed in
CombodoiTopAffected
  • <3.2.3
Fixed in
  • 3.2.3
GitHubcombodo/iToppkg:github/combodo/iTopOther threatsAffected
  • <3.2.3
Fixed in
  • 3.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Combodo iTop version 3.2.3 or later, where this vulnerability has been fixed. No other mitigation is required as the issue is resolved in the official patch.

Description

A vulnerability in Combodo iTop prior to version 3.2.3 allows sensitive information to be disclosed through error messages. This issue is classified under CWE-209, which involves generation of error messages containing sensitive information. The vulnerability has a low severity score and has been fixed in version 3.2.3.

References

Community reviews

Loading reviews…