# CVE-2026-92565: Rallly before 4.15.0 Information Disclosure via polls.get

> Unauthenticated attackers can retrieve sensitive invitee names and emails from polls via public links, bypassing privacy settings.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-36pr-h5jw-r82m

## What is CVE-2026-92565?

CVE-2026-92565 is a medium-severity vulnerability in lukevella rallly, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rallly before 4.15.0 contains an information disclosure vulnerability in the polls.get tRPC procedure that returns scheduled-event invitee names and email addresses to unauthenticated callers. Attackers can access a poll's urlId from public invite links to retrieve sensitive invitee information regardless of privacy settings.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-92565 being exploited?

There is no known exploitation of CVE-2026-92565 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92565 is a medium-severity vulnerability in lukevella rallly, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92565 in the wild and no public exploit code.

Affected product: lukevella rallly. 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-92565/ (Markdown: https://insights.sbomify.com/CVE-2026-92565/index.md)
```

## Sources

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

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