CVE-2026-127131

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

EUVD-2026-124530 ↗

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.
Alinto sogo < 5.12.13
fixed in 5.12.13
CWE-307 Improper Restriction of Excessive Authentication Attempts
ETK-2026-4290Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 45msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h17m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

SOGo versions before 5.12.13 do not apply failed-login limits to web TOTP verification attempts. An attacker who already has a user's password may repeatedly guess the second-factor code and potentially bypass two-factor authentication.

mitigation

Upgrade SOGo to version 5.12.13 or later. Until upgraded, reduce exposure to the web login service and monitor for repeated failed TOTP verification attempts.

fixed in 5.12.13

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.
–
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
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 15:56Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-12 15:56Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4290",
  "cve_id": "CVE-2026-127131",
  "display_id": "CVE-2026-127131",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-124530",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing TOTP rate limiting in SOGo web login",
  "summary": "SOGo versions before 5.12.13 do not apply failed-login limits to web TOTP verification attempts. An attacker who already has a user's password may repeatedly guess the second-factor code and potentially bypass two-factor authentication.",
  "mitigation": "Upgrade SOGo to version 5.12.13 or later. Until upgraded, reduce exposure to the web login service and monitor for repeated failed TOTP verification attempts.",
  "vendor": "Alinto",
  "product": "sogo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.12.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.12.13"
      ],
      "package_name": "sogo",
      "purl": null
    }
  ],
  "cwes": [
    307
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.40982066666667,
  "t0_at": "2026-11-12T15:56:31.256000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T15:56:31.256000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T15:56:31.256000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-127131"
    }
  }
}

published 2026-11-12 16:53Z
last change 2026-11-13 01:03Z

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.