ETK-2026-4601Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qqfr-626g-64rp ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
nuget:Duende.IdentityServer >= 8.0.0, < 8.0.11; >= 7.4.0, < 7.4.15; >= 7.3.0, < 7.3.6; >= 7.2.0, < 7.2.6; >= 7.1.0, < 7.1.4; >= 7.0.0, < 7.0.11
fixed in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4, 7.0.11
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-4601Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:nuget/Duende.IdentityServer
2d 04h 22msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −2.2dwaiting for further signals−2.2d
−2d
−1d
0

description

Duende.IdentityServer can incorrectly validate certain RSA-based DPoP proofs, weakening proof-key binding. An attacker who meets the affected token or client-configuration prerequisites may reuse a stolen DPoP-bound token, impersonate an affected client, or disrupt that client's DPoP authentication. Exposure is limited to RSA DPoP use or RSA JsonWebKey client secrets and related configurations.

mitigation

Upgrade Duende.IdentityServer to 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4, or 7.0.11, as appropriate for your release line. Until upgraded, avoid RSA DPoP keys and review RSA JsonWebKey client-secret and signing-key configurations.

fixed in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4, 7.0.11

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-16 17:18Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4601

{
  "etk_id": "ETK-2026-4601",
  "cve_id": null,
  "display_id": "ETK-2026-4601",
  "ghsa_id": "GHSA-qqfr-626g-64rp",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "DPoP key-binding validation flaw in Duende.IdentityServer",
  "summary": "Duende.IdentityServer can incorrectly validate certain RSA-based DPoP proofs, weakening proof-key binding. An attacker who meets the affected token or client-configuration prerequisites may reuse a stolen DPoP-bound token, impersonate an affected client, or disrupt that client's DPoP authentication. Exposure is limited to RSA DPoP use or RSA JsonWebKey client secrets and related configurations.",
  "mitigation": "Upgrade Duende.IdentityServer to 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4, or 7.0.11, as appropriate for your release line. Until upgraded, avoid RSA DPoP keys and review RSA JsonWebKey client-secret and signing-key configurations.",
  "vendor": "nuget",
  "product": "nuget:Duende.IdentityServer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.0.0, < 8.0.11"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "8.0.11"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.4.0, < 7.4.15"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "7.4.15"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.3.0, < 7.3.6"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "7.3.6"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.2.0, < 7.2.6"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "7.2.6"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.1.0, < 7.1.4"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "7.1.4"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, < 7.0.11"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "7.0.11"
      ],
      "package_name": "Duende.IdentityServer",
      "purl": "pkg:nuget/Duende.IdentityServer"
    }
  ],
  "cwes": [
    347
  ],
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.5257965,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-16T17:18:35+00:00",
      "days": -2.195363169386574,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:59:54.430199+00:00",
      "url": "https://github.com/DuendeSoftware/products/security/advisories/GHSA-qqfr-626g-64rp"
    }
  }
}

published 2026-11-16 17:30Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.