CVE-2025-59288
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper verification of cryptographic signature in Github: Playwright allows an unauthorized attacker to perform spoofing over an adjacent network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePlaywright contains a vulnerability where cryptographic signatures are not properly verified, allowing an attacker on an adjacent network to perform spoofing attacks. This could enable man-in-the-middle attacks where the attacker impersonates legitimate Playwright components or packages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.55.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Playwright versionRun `npm list playwright` in your project directory or `npx playwright --version` to display the installed versionAffected if The version shown is lower than 1.55.1 (e.g., 1.55.0, 1.54.x, etc.)
-
Verify package.json dependencyInspect your package.json file for the playwright version entry under "dependencies" or "devDependencies"Affected if The specified version is less than 1.55.1 (e.g., ^1.50.0, ~1.52.0, or any range resolving to <1.55.1)
-
Check package-lock.json version lockSearch package-lock.json for the "version" field within the playwright package entryAffected if The locked version is below 1.55.1
You are affected if any installed Playwright version resolves to less than 1.55.1, as this version range lacks proper cryptographic signature verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.55.1
Update Playwright to the latest version that includes proper cryptographic signature verification. Verify integrity of Playwright packages using published checksums or signatures before deployment.
1.55.1
- Check current Playwright version by running: npx playwright --version
- Update Playwright to the fixed version 1.55.1 by running: npm install [email protected] (or yarn add [email protected], or pnpm add [email protected])
- If you have @playwright/test as a separate dependency, also update it: npm install @playwright/[email protected]
- Verify the upgrade was successful by running: npx playwright --version and confirming the output shows 1.55.1
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data