GHSA-8fh9-c4jq-94h4: idunno.Bluesky, idunno.AtProto and idunno.AtProto.OAuthCallback Denial of Service Vulnerability
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: idunno.AtProto (NuGet) 1.7.0; idunno.AtProto.OAuthCallback (NuGet) 1.7.0; idunno.Bluesky (NuGet) 1.7.0.
Low priority for now. Upgrade to idunno.AtProto (NuGet) 1.7.0; idunno.AtProto.OAuthCallback (NuGet) 1.7.0; idunno.Bluesky (NuGet) 1.7.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: OSV
# idunno.Bluesky, idunno.AtProto and idunno.AtProto.OAuthCallback Denial of Service Vulnerability ## Impact The `Microsoft.Bcl.Memory` package, a transitive dependency of `idunno.AtProto` and `idunno.AtProto.OAuthCallback` had a Denial of Service security vulnerability, [CVE-2026-26127](https://github.com/dotnet/announcements/issues/384) ## Patches v1.7.0 updates the dependencies on `Duende.IdentityModel.OidcClient` and `Duende.IdentityModel.OidcClient.Extensions` which, in turn, updates their dependency on `Microsoft.Bcl.Memory` to 10.0.4, resolving the vulnerability. ## Workarounds No workarounds exist for this vulnerability. ## How to fix the issue To update your dependencies on `idunno.Bluesky`, `idunno.AtProto` and `idunno.AtProto.OAuthCallback`, ### Using the .NET CLI (Command Line Interface): * Open a terminal or command prompt in your project's directory. * To update a specific package to its latest version, use the following add package command: * If you are using `idunno.Bluesky` `dotnet package update idunno.Bluesky` * If you are using `idunno.AtProto` as a direct dependency `dotnet package update idunno.AtProto` * If you are using `idunno.AtProto.OAuthCallback` as a direct dependency `dotnet package update idunno.AtProto.OAuthCallback` ### Using the NuGet Package Manager Console in Visual Studio: * Open your project in Visual Studio. * Navigate to "Tools > NuGet Package Manager > Package Manager Console". * To update a specific package to its latest version, use the following Update-Package command: * If you are using `idunno.Bluesky` `Update-Package -Id idunno.Bluesky` * If you are using `idunno.AtProto` as a direct dependency `Update-Package -Id idunno.AtProto` * If you are using `idunno.AtProto.OAuthCallback` as a direct dependency `Update-Package -Id idunno.AtProto.OAuthCallback` ### NuGet Package Manager UI in Visual Studio: * Open your project in Visual Studio. * Right-click on your project in Solution Explorer and select "Manage NuGet Packages..." or navigate to "Project > Manage NuGet Packages". * In the NuGet Package Manager window, select the "Updates" tab. This tab lists packages with available updates from your configured package sources. * Select the package(s) you wish to update. You can choose a specific version from the dropdown or update to the latest available version. * Click the "Update" button. ## References * [Microsoft Security Advisory CVE-2026-26127 – .NET Denial of Service Vulnerability](https://github.com/dotnet/announcements/issues/384) * [CVE-2026-26127](https://www.cve.org/CVERecord?id=CVE-2026-26127)
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- EPSS
- —
- CWE
- CWE-129
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
|---|---|---|
| NuGet | idunno.AtProto | pkg:nuget/idunno.AtProto |
| NuGet | idunno.AtProto.OAuthCallback | pkg:nuget/idunno.AtProto.OAuthCallback |
| NuGet | idunno.Bluesky | pkg:nuget/idunno.Bluesky |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| NuGet | idunno.AtProto | before 1.7.0 | 1.7.0 |
| NuGet | idunno.AtProto.OAuthCallback | before 1.7.0 | 1.7.0 |
| NuGet | idunno.Bluesky | before 1.7.0 | 1.7.0 |
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 |
|---|---|---|
| NuGet:idunno.AtProto | 1.7.0 | Package registry (OSV) |
| NuGet:idunno.AtProto.OAuthCallback | 1.7.0 | Package registry (OSV) |
| NuGet:idunno.Bluesky | 1.7.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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv
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
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.