CVE-2026-6647

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

GHSA-rxrw-f2xj-7fjx ↗EUVD-2026-112401 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
WSO2 Identity Server >= 7.2.0, < 7.2.0.21; >= 7.0.385, < 7.0.385.17
fixed in 7.2.0.21, 7.0.385.17
ETK-2026-2924Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 17msince last run
1h 00mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h06m
0
+2h
+4h
+8h
+10h
+12h

description

WSO2 Identity Server can fail to revoke OAuth tokens when username case handling differs between the user store and identity database. An attacker holding an access or refresh token for a mixed-case username may retain access until that token expires. The issue requires a case-insensitive user store paired with a case-sensitive identity-data database.

mitigation

Align username case-sensitivity settings between the user store and identity-data database to avoid the affected mismatch. Until a vendor fix is identified, reduce token lifetimes and review or restrict active tokens for mixed-case usernames.

fixed in 7.2.0.21, 7.0.385.17

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 00m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 19:21Z
Δ 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-10-28 19:21Z
    ghsa: trigger signal, started the run
  2. 2026-10-28 19:21Z

this entry in the feed

GET /api/v1/feed/CVE-2026-6647

{
  "etk_id": "ETK-2026-2924",
  "cve_id": "CVE-2026-6647",
  "display_id": "CVE-2026-6647",
  "ghsa_id": "GHSA-rxrw-f2xj-7fjx",
  "euvd_id": "EUVD-2026-112401",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OAuth token revocation bypass in WSO2 Identity Server",
  "summary": "WSO2 Identity Server can fail to revoke OAuth tokens when username case handling differs between the user store and identity database. An attacker holding an access or refresh token for a mixed-case username may retain access until that token expires. The issue requires a case-insensitive user store paired with a case-sensitive identity-data database.",
  "mitigation": "Align username case-sensitivity settings between the user store and identity-data database to avoid the affected mismatch. Until a vendor fix is identified, reduce token lifetimes and review or restrict active tokens for mixed-case usernames.",
  "vendor": "WSO2",
  "product": "WSO2 Identity Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.2.0, < 7.2.0.21"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.2.0.21"
      ],
      "package_name": "WSO2 Identity Server",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.385, < 7.0.385.17"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.0.385.17"
      ],
      "package_name": "org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 59.909318383333336,
  "t0_at": "2026-10-28T19:21:35.702000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T19:21:35.702000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T19:21:35.702000+00:00",
      "url": "https://github.com/advisories/GHSA-rxrw-f2xj-7fjx"
    }
  }
}

published 2026-10-29 00:28Z
last change 2026-10-29 04:54Z

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.