CVE-2026-57948
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 · uneditedPinpoint through version 3.1.0 contains an insecure session management vulnerability that allows attackers to access the pinpointJwt session cookie due to missing HttpOnly and Secure attributes, enabling JavaScript access via document.cookie and cleartext transmission over HTTP. Attackers can exploit stored or reflected cross-site scripting vulnerabilities to exfiltrate the session token or intercept it through network sniffing to perform session hijacking.
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 · high confidencePinpoint through version 3.1.0 sets the pinpointJwt session cookie without the HttpOnly and Secure flags. The missing HttpOnly attribute allows JavaScript to access the cookie via document.cookie, enabling XSS-based token exfiltration. The missing Secure attribute allows the cookie to be transmitted in cleartext over HTTP, permitting network interception.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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.
-
Identify Pinpoint deploymentLocate Pinpoint installation in your environment - check application servers, containers, or services running Pinpoint agents or collectorsAffected if Pinpoint is deployed in the environment
-
Determine Pinpoint versionCheck the installed Pinpoint version (library, agent, or collector version depending on component) and compare to 3.1.0Affected if Version is 3.1.0 or earlier (the vulnerability affects through version 3.1.0)
-
Identify pinpointJwt cookieMonitor HTTP responses from Pinpoint components and look for a cookie named 'pinpointJwt' being setAffected if A cookie named pinpointJwt is being created in session responses
-
Inspect HttpOnly flag on pinpointJwtExamine the Set-Cookie header or browser dev tools for the pinpointJwt cookie and check if the HttpOnly attribute is presentAffected if The HttpOnly attribute is missing from the pinpointJwt cookie
-
Inspect Secure flag on pinpointJwtExamine the Set-Cookie header or browser dev tools for the pinpointJwt cookie and check if the Secure attribute is presentAffected if The Secure attribute is missing from the pinpointJwt cookie
Your environment is affected if you are running Pinpoint version 3.1.0 or earlier and the pinpointJwt session cookie is missing either the HttpOnly or Secure attribute.
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.
From vendor dataConfigure the pinpointJwt session cookie with both HttpOnly and Secure flags at the point of cookie creation/session initialization to prevent client-side script access and enforce encrypted transmission.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57948 — 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-2026-57948 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