CVE-2026-41575: In th30d4y/IP from version 1.0.1 to before version 2.0.1, a DOM-Based Cross-Site Scripting (XSS) vulnerability

Q: How do I fix CVE-2026-41575?

w4nn4d13\/ip: upgrade to 2.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-41575 being exploited?

CVE-2026-41575 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-41575 affect?

CVE-2026-41575 affects w4nn4d13\/ip. Severity is medium (CVSS 6.1). In th30d4y/IP from version 1.0.1 to before version 2.0.1, a DOM-Based Cross-Site Scripting (XSS) vulnerability was identified in an IP Reputation Checker application. Unsanitized user input was directly rendered in the browser, allowing att

Q: How urgent is CVE-2026-41575?

Priority 23/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2026-41575 is a medium-severity flaw (CVSS 6.1) affecting w4nn4d13\/ip. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In th30d4y/IP from version 1.0.1 to before version 2.0.1, a DOM-Based Cross-Site Scripting (XSS) vulnerability was identified in an IP Reputation Checker application. Unsanitized user input was directly rendered in the browser, allowing attackers to execute arbitrary JavaScript. This issue has been patched in version 2.0.1.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-79, CWE-80
Published	2026-05-08
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: th30d4y

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-08 15:16 UTCPublished CVE record published
2026-06-17 10:46 UTCUpdated Record last modified

th30d4y w4nn4d13\/ip UPGRADE

Affected: >= 1.0.1 and < 2.0.1

Fixed in: 2.0.1

Safe to downgrade to: a release before 1.0.1

1. Check installed version

npm ls w4nn4d13ip

2. UPGRADE to 2.0.1

npm install w4nn4d13ip@">=2.0.1"

3. If no update is available yet, DOWNGRADE to a release before 1.0.1

npm view w4nn4d13ip versions npm install w4nn4d13ip@"<1.0.1"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41575?

w4nn4d13\/ip: upgrade to 2.0.1. Exact commands for each OS are on this page.

Is CVE-2026-41575 being exploited?

CVE-2026-41575 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41575 affect?

CVE-2026-41575 affects w4nn4d13\/ip. Severity is medium (CVSS 6.1). In th30d4y/IP from version 1.0.1 to before version 2.0.1, a DOM-Based Cross-Site Scripting (XSS) vulnerability was identified in an IP Reputation Checker application. Unsanitized user input was directly rendered in the browser, allowing att

How urgent is CVE-2026-41575?

Priority 23/100. No elevated risk signals yet.

References

← Back to latest CVEs