# CVE-2021-26905: Information disclosure in n/a

> An attacker can access TLS private keys due to improper validation of authenticated log file requests in 1Password SCIM Bridge.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-826j-q2q2-rcq4

## What is CVE-2021-26905?

CVE-2021-26905 is a medium-severity vulnerability in n/a, published on 8 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

1Password SCIM Bridge before 1.6.2 mishandles validation of authenticated requests for log files, leading to disclosure of a TLS private key.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-26905?

It affects 1 product.


Products: 1password Scim Bridge.

## How do I fix CVE-2021-26905?

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

## Is CVE-2021-26905 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26905 and fix it if it is affected.

What it is: CVE-2021-26905 is a medium-severity vulnerability in n/a, published on 8 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26905 in the wild and no public exploit code.

Affected product: n/a. 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-2021-26905/ (Markdown: https://insights.sbomify.com/CVE-2021-26905/index.md)
```

## Sources

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

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