NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm.NET NuGet
Not in CISA KEV
MEDIUM severity

CVE-2024-26318 — @serenity-is/corelib

MEDIUM

CVE-2024-26318 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in @serenity-is/corelib. A fix is available for @serenity-is/corelib — see the affected versions and patch details below.

Cross-site Scripting in Serenity

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-26318.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk
0.00%0.30%0.59%0.89%0.1%0.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@serenity-is/corelibnpm
116downloads / week

Description

Serenity before 6.8.0 allows XSS via an email link because LoginPage.tsx permits return URLs that do not begin with a / character.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@serenity-is/coreliball versions6.8.0npm install @serenity-is/corelib@6.8.0
.NETNuGetSerenity.Net.Coreall versions6.8.0dotnet add package Serenity.Net.Core --version 6.8.0

Affected Products

1 product · 1 configurations
Application
serenityserenity
< 6.8.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @serenity-is/corelib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @serenity-is/corelib to 6.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-26318 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Serenity before 6.8.0 allows XSS via an email link because LoginPage.tsx permits return URLs that do not begin with a / character.
O3 Security · Impact-Aware SCA

Is CVE-2024-26318 in your dependencies?

Find it across npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-26318: @serenity-is/corelib XSS — Fixed in 6.8.0