CVE-2026-100169

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-101295 (ENISA EUVD) · GHSA-5qw5-54v9-9g7q (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to Prowler 5.35.0 or later."

Improper Authentication in the social account linking path of the Prowler API in Prowler from 5.4.0 before 5.35.0 allows a remote unauthenticated attacker to obtain persistent access to the account of a user who has not yet registered, because ProwlerSocialAccountAdapter.pre_social_login() in api/src/backend/api/adapters.py links a Google or GitHub login to any existing local account that has the same email address as the one returned by the provider, without requiring that the address has been verified by the provider or on the existing account, and without any other check that both accounts belong to the same person. Self registration is open and the new account is usable at once, because UserViewSet.get_permissions() in api/src/backend/api/v1/views.py grants AllowAny to the create action, ACCOUNT_EMAIL_VERIFICATION is set to none in api/src/backend/config/settings/social_login.py, and the Django ModelBackend checks only the password and is_active, not the django-allauth EmailAddress record. An attacker who registers an email address before its owner keeps the password set at registration after the link is made, because sociallogin.connect() does not reset the password and does not disable the existing account, and the owner who later signs in with Google or GitHub is logged into the attacker's account. django-allauth makes the same email based link on its own, because SOCIALACCOUNT_EMAIL_AUTHENTICATION and SOCIALACCOUNT_EMAIL_AUTHENTICATION_AUTO_CONNECT are both set to True in the same settings module. This gives the attacker the cloud provider credentials, scan findings and tenant memberships held in the account.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 16, 2026

Advisory Details (5)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
Web page

cve-2026-100169 · Account pre-hijacking in the Prowler API through email based social account linking without verification | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-100169-prowler-account-pre-hijacking
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

SAML Domain Claiming Enables Cross-Tenant Account Takeover · Advisory · prowler-cloud/prowler · GitHub

https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp
GitHub release Patch Available

Prowler 5.35.0

Patch available: prowler-cloud/prowler 5.35.0

https://github.com/prowler-cloud/prowler/releases/tag/5.35.0
GitHub pull request

fix(api): strengthen social account linking

Fix merged in prowler-cloud/prowler PR #12013 on 2026-07-16 — awaiting tagged release

https://github.com/prowler-cloud/prowler/pull/12013
GitHub commit

commit 0f31f1a3c2da (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit 0f31f1a3c2da — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/0f31f1a3c2daa05b4d77a78f451e3fbfb3fe3411

Vendor Advisories for CVE-2026-100169(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
prowler-cloud0.0.0rc1 ... 5.9.2 (191 versions)
  • every version up to 5.30.3: fixed in 5.30.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-27 20:35 UTCEG score recompute
  7. 2026-10-27 20:35 UTCGHSA enrichmentGHSA-5qw5-54v9-9g7q · GitHub severity HIGH
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-25 15:58 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-20 19:17 UTCEG score recompute
  17. 2026-10-20 19:17 UTCGHSA enrichmentGHSA-5qw5-54v9-9g7q · GitHub severity HIGH
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-10-16 20:10 UTCGHSA enrichmentGHSA-5qw5-54v9-9g7q · GitHub severity HIGH
  24. 2026-10-16 17:11 UTCEG score recompute
  25. 2026-10-16 17:11 UTCGHSA enrichmentGHSA-5qw5-54v9-9g7q · GitHub severity HIGH
Show 7 more
  1. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  2. 2026-10-16 15:46 UTCEG score recompute
  3. 2026-10-16 15:46 UTCGHSA enrichmentGHSA-5qw5-54v9-9g7q · GitHub severity HIGH
  4. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  5. 2026-10-14 17:13 UTCEG score recompute
  6. 2026-10-14 16:11 UTCEG score recomputeFirst assessed: 7.6 HIGH
  7. 2026-10-14 16:09 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

PyPI:prowler-cloud

Frequently asked(5)

What is CVE-2026-100169?
CVE-2026-100169 is a high-severity vulnerability; its CVE record was published on October 14, 2026. Improper Authentication in the social account linking path of the Prowler API in Prowler from 5.4.0 before 5.35.0 allows a remote unauthenticated attacker to obtain persistent access to the account of a user who has not yet registered, because ProwlerSocialAccountAdapter.pre_social_login() in…
When was the CVE record for CVE-2026-100169 published?
The CVE record for CVE-2026-100169 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-100169 actively exploited?
CVE-2026-100169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100169?
CVE-2026-100169 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100169?
A fix for CVE-2026-100169 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to Prowler 5.35.0 or later." The vendor advisories EchelonGraph has for CVE-2026-100169 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-100169

Explore →

Is Your Infrastructure Affected by CVE-2026-100169?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs