dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-57947

HIGH · 8.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 · unedited
Pinpoint through 3.1.0 contains a server-side request forgery vulnerability in the webhook registration endpoint that allows authenticated users to register internal URLs due to missing SSRF protection. Attackers can trigger alarm threshold breaches to force the server to issue POST requests to internal hosts and metadata endpoints, enabling unauthorized access to internal network resources.

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 confidence

Pinpoint up to v3.1.0 contains an SSRF vulnerability in its webhook registration endpoint where authenticated users can register arbitrary URLs including internal network addresses without proper validation. Attackers exploit this by triggering alarm threshold breaches, forcing the server to issue POST requests to internal hosts and cloud metadata endpoints.

MitigationUpgrade to a version beyond 3.1.0 that implements SSRF protection, or implement URL allowlisting and network segmentation to block requests to internal IP ranges and metadata endpoints.

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pinpoint installation and version
    Locate the Pinpoint installation directory and check the version file or WAR/WAR metadata. Common locations: /opt/pinpoint, /usr/local/pinpoint, or within a Java application server webapp directory. Run: grep -r 'version' or check pom.xml, build.gradle, or version.info files.
    Affected if The installed version is 3.1.0 or any version prior to it.
  2. Verify webhook feature is enabled
    Search for webhook-related configuration files in the Pinpoint setup. Look for files named webhook.conf, webhook.properties, or similar in config directories. Check for entries enabling webhook functionality (e.g., webhook.enabled=true, hook.enable=1).
    Affected if Webhook feature is enabled in the configuration files.
  3. Inspect registered webhook URLs
    Examine the Pinpoint database or configuration store for registered webhook endpoints. Query the webhook or hook tables if using a database backend, or inspect the webhook configuration YAML/JSON files.
    Affected if Any registered webhook URL points to a private/internal IP range (127.0.0.1, 10.x.x.x, 172.16-31.x.x, 192.168.x.x), localhost, or known cloud metadata endpoints (e.g., 169.254.169.254 for AWS/GCP/Azure).
  4. Check authentication and authorization for webhook registration
    Review Pinpoint user roles and permissions configuration. Determine if authenticated users with standard or low-privilege accounts can register new webhooks without administrative approval.
    Affected if Standard authenticated users have permission to create or modify webhook registrations without restriction.
  5. Confirm network accessibility to internal resources
    Verify that the Pinpoint server has network routing to internal network ranges and cloud metadata IP addresses. Run connectivity tests: curl -I http://127.0.0.1, curl -I http://169.254.169.254 (cloud metadata), or trace routes to RFC1918 addresses.
    Affected if The Pinpoint server can initiate outbound HTTP/HTTPS connections to internal/private network addresses or cloud metadata endpoints.

You are affected if Pinpoint version is 3.1.0 or earlier, the webhook feature is enabled, and either internal/private URLs are already registered as webhooks or standard users have the ability to register arbitrary webhook targets without restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version beyond 3.1.0 that implements SSRF protection, or implement URL allowlisting and network segmentation to block requests to internal IP ranges and metadata endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57947 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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