Vulnerabilities
Summary — last 7 days
New vulnerabilities5,290▲ 2,541 vs. last week
Critical / high2,969▲ 1,639 vs. last week
New active exploitation (KEV)6▼ 2 vs. last week
Unscored (no CVSS)223▲ 49 vs. last week
5 results, sorted by published date (most recent first)
| CVE | Status | Severity | EPSS | Active exploitation | Affected technologies | Published ▼ | Modified | Description |
|---|---|---|---|---|---|---|---|---|
| Modified | High (7.5) | 8.5% | 💥 Exploit | Tippingpoint Tipping Point3com Tippingpoint IPS TOS | 7/11/2007 | 6/16/2026 | TippingPoint IPS before 20070710 does not properly handle a hex-encoded alternate Unicode '/' (slash) character, which might allow remote attackers to send certain network traffic and avoid detection, as demonstrated by a cmd.exe attack. | |
| Modified | High (7.5) | 2.1% | — | 3com Tippingpoint IPS TOS | 7/11/2007 | 6/16/2026 | Unspecified vulnerability in TOS 2.1.x, 2.2.x before 2.2.5, and 2.5.x before 2.5.2 on TippingPoint IPS allows remote attackers to avoid detection by sending certain fragmented packets. | |
| Modified | High (7.8) | 1.7% | — | 3com Tippingpoint IPS | 4/25/2007 | 6/16/2026 | 3Com TippingPoint IPS allows remote attackers to cause a denial of service (device hang) via a flood of packets on TCP port 80 with sequentially increasing source ports, related to a "badly written loop." NOTE: the vendor disputes this issue, stating that the product has "performed as expected with no DoS emerging. | |
| Modified | Medium (5) | 1.9% | — | 3com Tippingpoint IPS TOS | 7/26/2006 | 6/16/2026 | TippingPoint IPS running the TippingPoint Operating System (TOS) before 2.2.4.6519 allows remote attackers to "force the device into layer 2 fallback (L2FB)", causing a denial of service (page fault), via a malformed packet. | |
| Modified | Medium (5) | 1.9% | — | 3com Tippingpoint IPS TOS | 1/22/2006 | 6/16/2026 | TippingPoint Intrusion Prevention System (IPS) TOS before 2.1.4.6324, and TOS 2.2.x before 2.2.1.6506, allow remote attackers to cause a denial of service (CPU consumption) via an unknown vector, probably involving an HTTP request with a negative number in the Content-Length header. |