CVE-2026-62126

validated

GHSA-q866-82pg-8qrm ↗EUVD-2026-116774 ↗

check availablenot proven exploitable

cve.orgpublic pockev

miniOrange SAML SP Single Sign On <= 6.1.0

CWE-770 Allocation of Resources Without Limits or Throttling

ETK-2026-3472, permanent identifier

cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

+21mTTV

<1mAI analysis

Check if you are vulnerable

timeline

0 = trigger signal

trigger signal (cve.org) +0mcheck available+21magent stopped

+5min

+10min

+15min

description

miniOrange SAML SP Single Sign On versions through 6.1.0 are affected by an HTTP resource-exhaustion flaw. An unauthenticated remote attacker may cause denial of service by making requests that consume excessive server resources; access to the affected HTTP service is required.

mitigation

Restrict access to the affected HTTP service and enforce request-rate, request-size, and concurrency limits at the web server or reverse proxy. Monitor for a vendor update, as no fixed version is recorded in the advisory.

check

available

exploit

automation

deterministic

auth required

EPSS

–

agent run time

<1m

cve.org record, t = 0

2026-11-04 08:00Z

Δ to public poc

–

Δ to kev

–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

2026-11-04 08:00Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-62126
2026-11-04 08:21Z
Patchstack ships a detection
patchstack · https://patchstack.com/database/vulnerability/miniorange-saml-20-single-sign-on/wordpress-saml-sp-single-sign-on-plugin-6-1-0-denial-of-service-attack-vulnerability?_a_id=500

this entry in the feed

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

{
  "etk_id": "ETK-2026-3472",
  "cve_id": "CVE-2026-62126",
  "display_id": "CVE-2026-62126",
  "ghsa_id": "GHSA-q866-82pg-8qrm",
  "euvd_id": "EUVD-2026-116774",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource-exhaustion denial of service in miniOrange SAML SP",
  "summary": "miniOrange SAML SP Single Sign On versions through 6.1.0 are affected by an HTTP resource-exhaustion flaw. An unauthenticated remote attacker may cause denial of service by making requests that consume excessive server resources; access to the affected HTTP service is required.",
  "mitigation": "Restrict access to the affected HTTP service and enforce request-rate, request-size, and concurrency limits at the web server or reverse proxy. Monitor for a vendor update, as no fixed version is recorded in the advisory.",
  "vendor": "miniOrange",
  "product": "SAML SP Single Sign On",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 6.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "miniorange-saml-20-single-sign-on",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.4018717666666667,
  "t0_at": "2026-11-04T08:00:16.984000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T08:21:16.160580+00:00",
      "days": 0.01457380300925926,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T08:00:16.984000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-04T08:00:16.984000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T08:00:16.984000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-62126"
    }
  }
}

published 2026-11-04 08:20Z
last change 2026-11-04 09:41Z

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.