NVD / CVE Program· CNA GitHub_M

CVE-2022-23485: Invite code reuse via cookie manipulation in sentry

Noroxi assessment

Priority: Monitor (action score 14/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: getsentry sentry 22.11.0.
Severity is disputed: the assigning authority (CNA) scores it 6.4, NVD 3.7.

Low priority for now. Upgrade to getsentry sentry 22.11.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Sentry is an error tracking and performance monitoring platform. In versions of the sentry python library prior to 22.11.0 an attacker with a known valid invite link could manipulate a cookie to allow the same invite link to be reused on multiple accounts when joining an organization. As a result an attacker with a valid invite link can create multiple users and join an organization they may not have been originally invited to. This issue was patched in version 22.11.0. Sentry SaaS customers do not need to take action. Self-hosted Sentry installs on systems which can not upgrade can disable the invite functionality until they are ready to deploy the patched version by editing their `sentry.conf.py` file (usually located at `~/.sentry/`).

LowCVSS 3.7 · v3.1—No exploit Fix available

Pre-auth

Published: Dec 9, 2022
Updated: Jun 17, 2026
EPSS: 0.4% · 39th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 3.7
CNA · GitHub_M: 6.4; 2.7 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
sentry	sentry	cpe:2.3:a:sentry:sentry

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

sentry sentry20.6.0 and later · up to 22.10.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

getsentry sentry
- >= 20.6.0, < 22.11.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
PyPI	sentry	from 20.6.0 · before 22.11.0	22.11.0

Same product

sentry: all records

Other highest-scoring records for the same primary product.

CVE-2026-42354Sentry: Improper authentication on SAML SSO process allows user identity linking
39Monitor
CVE-2026-27197Sentry: Improper Authentication on SAML SSO process allows user identity linking
36Monitor
CVE-2021-47935Sentry 8.2.0 Remote Code Execution via Pickle Deserialization
34Monitor

Published before and after this one in the same product

Later →CVE-2023-36826Jul 25, 2023 · Sentry vulnerable to improper authorization on debug and artifact file downloads
26Monitor
Later →CVE-2023-39349Aug 7, 2023 · Sentry vulnerable to privilege escalation via ApiTokensEndpoint
32Monitor
Later →CVE-2023-39531Aug 9, 2023 · Sentry vulnerable to incorrect credential validation on OAuth token requests
27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
getsentry sentry	22.11.0 · description	Vendor (CNA)
PyPI:sentry	22.11.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/getsentry/sentry/security/advisories/GHSA-jv85-mqxj-3f9j

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records