# CVE-2026-57948: Pinpoint - Insecure Session Cookie Attributes in pinpointJwt

> Attackers can hijack sessions by stealing the pinpointJwt cookie via XSS or sniffing due to missing HttpOnly and Secure attributes.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-f4g5-7fg3-8rw6

## What is CVE-2026-57948?

CVE-2026-57948 is a high-severity vulnerability in pinpoint-apm pinpoint, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Pinpoint 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.

Weakness: CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

## Which versions are affected by CVE-2026-57948?


## How do I fix CVE-2026-57948?

No fix has been published for CVE-2026-57948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57948 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57948 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57948 and fix it if it is affected.

What it is: CVE-2026-57948 is a high-severity vulnerability in pinpoint-apm pinpoint, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57948 exists.

Affected product: pinpoint-apm pinpoint. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57948/ (Markdown: https://insights.sbomify.com/CVE-2026-57948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57948
- OSV: https://osv.dev/vulnerability/CVE-2026-57948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57948/
Summaries are generated and may contain mistakes; the official description above is the record.