Skip to main content
CVE-2025-28041VulnerabilityPublished Updated

CVE-2025-28041: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
itranswarp up to 2.19
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2025-28041, European organizations should first conduct an immediate inventory to identify any use of itranswarp framework versions up to 2.19 within their software stack. Until an official patch is released, organizations should implement compensating controls such as deploying Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized access attempts targeting the doFilter function or sensitive endpoints. Network segmentation should be enforced to limit exposure of vulnerable services to untrusted networks. Additionally, organizations should review and harden access control policies at the application and infrastructure levels, ensuring strict authentication and authorization checks are in place. Monitoring and logging should be enhanced to detect anomalous access patterns indicative of exploitation attempts. Where possible, consider temporary disabling or restricting access to vulnerable components. Engage with the itranswarp vendor or community to obtain updates on patches or security advisories. Finally, conduct security awareness training for developers and administrators to recognize and remediate access control weaknesses in custom code.

Description

Incorrect access control in the doFilter function of itranswarp up to 2.19 allows attackers to access sensitive components without authentication.

References

Community reviews

Loading reviews…