PYSEC-2026-1915

Vulnerability from pysec - Published: 2026-07-07 11:45 - Updated: 2026-07-07 17:25
VLAI
Details

Impact

An attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account.

Remediation

  • Sentry SaaS customers do not need to take any action. Those with the highest risk will be contacted directly by Sentry.
  • Self-hosted installations should upgrade to version 23.7.2 or higher.

Workarounds

There are no direct workarounds, but users should review applications authorized on their account (User Settings > Authorized Applications) and remove any that are no longer needed.

Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N
Impacted products
Name purl
sentry pkg:pypi/sentry
Aliases
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "sentry",
        "purl": "pkg:pypi/sentry"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10.0.0"
            },
            {
              "fixed": "23.7.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "10.0.0",
        "10.0.1",
        "20.10.1",
        "20.11.0",
        "20.11.1",
        "20.12.0",
        "20.12.1",
        "20.6.0",
        "20.7.0",
        "20.7.1",
        "20.7.2",
        "20.8.0",
        "21.1.0",
        "21.10.0",
        "21.11.0",
        "21.12.0",
        "21.2.0",
        "21.3.0",
        "21.3.1",
        "21.4.0",
        "21.4.1",
        "21.5.0",
        "21.5.1",
        "21.6.0",
        "21.6.1",
        "21.6.2",
        "21.6.3",
        "21.7.0",
        "21.8.0",
        "21.9.0",
        "22.1.0",
        "22.10.0",
        "22.11.0",
        "22.12.0",
        "22.2.0",
        "22.3.0",
        "22.4.0",
        "22.5.0",
        "22.6.0",
        "22.7.0",
        "22.8.0",
        "22.9.0",
        "23.1.0",
        "23.1.1",
        "23.2.0",
        "23.3.0",
        "23.3.1",
        "23.4.0",
        "23.5.0",
        "23.5.1",
        "23.5.2",
        "23.6.0",
        "23.6.1",
        "23.6.2",
        "23.7.0",
        "23.7.1"
      ]
    }
  ],
  "aliases": [
    "CVE-2023-39531",
    "GHSA-hgj4-h2x3-rfx4"
  ],
  "details": "### Impact\n\nAn attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account. \n\n### Remediation\n\n- **Sentry SaaS** customers do not need to take any action. Those with the highest risk will be contacted directly by Sentry.\n- **Self-hosted installations** should upgrade to version 23.7.2 or higher.\n\n### Workarounds\n\nThere are no direct workarounds, but users should review applications authorized on their account (_User Settings \u003e Authorized Applications_) and remove any that are no longer needed.\n\n",
  "id": "PYSEC-2026-1915",
  "modified": "2026-07-07T17:25:22.971708Z",
  "published": "2026-07-07T11:45:22.244062Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/getsentry/sentry/security/advisories/GHSA-hgj4-h2x3-rfx4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39531"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/getsentry/sentry"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/sentry"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-hgj4-h2x3-rfx4"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Sentry vulnerable to incorrect credential validation on OAuth token requests"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.