# CVE-2025-26468: CyberData 011209 SIP Emergency Intercom Missing Authentication for Critical Function

> Unauthenticated attackers can access critical functions on CyberData SIP Emergency Intercoms, causing denial-of-service or system disruption.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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:** 9 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-82vq-mq3h-xx6f

## What is CVE-2025-26468?

CVE-2025-26468 is a high-severity missing authorization vulnerability in CyberData 011209 SIP Emergency Intercom, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CyberData 
011209 

Intercom exposes features that could allow an unauthenticated to gain 
access and cause a denial-of-service condition or system disruption.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-26468?

It affects 1 product.


Products: Cyberdata 011209 Sip Emergency Intercom.

## How do I fix CVE-2025-26468?

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

## Is CVE-2025-26468 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26468 and fix it if it is affected.

What it is: CVE-2025-26468 is a high-severity missing authorization vulnerability in CyberData 011209 SIP Emergency Intercom, published on 9 Jun 2025. 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-2025-26468 in the wild and no public exploit code.

Affected product: CyberData 011209 SIP Emergency Intercom. 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-2025-26468/ (Markdown: https://insights.sbomify.com/CVE-2025-26468/index.md)
```

## Sources

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

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