CVE-2026-86322

validatingZero is analyzing and reversing it now.

GHSA-h4jq-48pm-fr95 ↗EUVD-2026-124675 ↗

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.
Red Hat Satellite 6
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-4320Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Foreman, including the API layer used by Red Hat Satellite 6, does not properly authorize the target account when issuing personal access tokens. A user permitted to create such tokens may obtain credentials for another account and impersonate it, including a privileged account.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict the create_personal_access_tokens permission to only fully trusted administrators until an update is available. Review and revoke unexpected personal access tokens, particularly for privileged accounts; no fixed version is recorded in the supplied advisory data.

check
building now
exploit
not yet
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.
–
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
57m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 20:19Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-12 20:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4320",
  "cve_id": "CVE-2026-86322",
  "display_id": "CVE-2026-86322",
  "ghsa_id": "GHSA-h4jq-48pm-fr95",
  "euvd_id": "EUVD-2026-124675",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Foreman personal-access-token API",
  "summary": "Foreman, including the API layer used by Red Hat Satellite 6, does not properly authorize the target account when issuing personal access tokens. A user permitted to create such tokens may obtain credentials for another account and impersonate it, including a privileged account.",
  "mitigation": "Restrict the `create_personal_access_tokens` permission to only fully trusted administrators until an update is available. Review and revoke unexpected personal access tokens, particularly for privileged accounts; no fixed version is recorded in the supplied advisory data.",
  "vendor": "Red Hat",
  "product": "Red Hat Satellite 6",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "foreman",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 57.08642715,
  "t0_at": "2026-11-12T20:19:29.433000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T20:19:29.433000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T20:19:29.433000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86322"
    }
  }
}

published 2026-11-12 21:04Z
last change 2026-11-12 23:56Z

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.