CVE-2026-32825 (GCVE-0-2026-32825)

Vulnerability from cvelistv5 – Published: 2026-07-20 16:15 – Updated: 2026-07-20 18:06
VLAI
Title
dataCycle No Brute-Force Protection On Web And API Login Endpoints
Summary
dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, the application accepts unlimited password guesses against both the browser login flow and the JSON login endpoint. The source code enables Devise's `:lockable` module on the user model but explicitly disables both lock and unlock strategies, and no request throttling or rate-limiting layer was identified in the Rails code. This creates a direct online password-guessing risk: - valid user accounts can be attacked continuously without temporary lockout - the same weakness is reachable through both `/users/sign_in` and `/api/v4/auth/login` - successful guessing yields a normal session cookie in the HTML flow or a fresh JWT in the API flow - the API endpoint is especially attractive for automation because it requires no CSRF token This has been patched in version 26.06.08.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-20 18:06 UTC
CWE
  • CWE-307 - Improper Restriction of Excessive Authentication Attempts
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 7840 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
datacycle-engine dataCycle-CORE Affected: <= 25.07.3
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-32825",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-20T18:06:20.638881Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-07-20T18:06:24.323Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "dataCycle-CORE",
          "vendor": "datacycle-engine",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c= 25.07.3"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, the application accepts unlimited password guesses against both the browser login flow and the JSON login endpoint. The source code enables Devise\u0027s `:lockable` module on the user model but explicitly disables both lock and unlock strategies, and no request throttling or rate-limiting layer was identified in the Rails code. This creates a direct online password-guessing risk:\n- valid user accounts can be attacked continuously without temporary lockout\n- the same weakness is reachable through both `/users/sign_in` and `/api/v4/auth/login`\n- successful guessing yields a normal session cookie in the HTML flow or a fresh JWT in the API flow\n- the API endpoint is especially attractive for automation because it requires no CSRF token\n\nThis has been patched in version 26.06.08."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-307",
              "description": "CWE-307: Improper Restriction of Excessive Authentication Attempts",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-20T16:15:37.377Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-736f-cqq3-ccgf",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-736f-cqq3-ccgf"
        }
      ],
      "source": {
        "advisory": "GHSA-736f-cqq3-ccgf",
        "discovery": "UNKNOWN"
      },
      "title": "dataCycle No Brute-Force Protection On Web And API Login Endpoints"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-32825",
    "datePublished": "2026-07-20T16:15:37.377Z",
    "dateReserved": "2026-03-16T17:35:36.697Z",
    "dateUpdated": "2026-07-20T18:06:24.323Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-32825",
      "date": "2026-11-15",
      "epss": "0.00342",
      "percentile": "0.28171"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "product": "dataCycle-CORE",
                "vendor": "datacycle-engine",
                "versions": [
                  {
                    "status": "affected",
                    "version": "\u003c= 25.07.3"
                  }
                ]
              }
            ],
            "source": "security-advisories@github.com"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, the application accepts unlimited password guesses against both the browser login flow and the JSON login endpoint. The source code enables Devise\u0027s `:lockable` module on the user model but explicitly disables both lock and unlock strategies, and no request throttling or rate-limiting layer was identified in the Rails code. This creates a direct online password-guessing risk:\n- valid user accounts can be attacked continuously without temporary lockout\n- the same weakness is reachable through both `/users/sign_in` and `/api/v4/auth/login`\n- successful guessing yields a normal session cookie in the HTML flow or a fresh JWT in the API flow\n- the API endpoint is especially attractive for automation because it requires no CSRF token\n\nThis has been patched in version 26.06.08."
          },
          {
            "lang": "es",
            "value": "dataCycle es un sistema de gesti\u00f3n de datos para almacenar, gestionar, buscar, encontrar y distribuir datos de forma centralizada. En dataCycle-CORE, el m\u00f3dulo que maneja el procesamiento central y las reglas del framework, antes e incluyendo la versi\u00f3n 25.07.3, la aplicaci\u00f3n acepta intentos ilimitados de contrase\u00f1a tanto contra el flujo de inicio de sesi\u00f3n del navegador como contra el endpoint de inicio de sesi\u00f3n JSON. El c\u00f3digo fuente habilita el m\u00f3dulo \u2019:lockable\u2019 de Devise en el modelo de usuario pero deshabilita expl\u00edcitamente ambas estrategias de bloqueo y desbloqueo, y no se identific\u00f3 ninguna capa de limitaci\u00f3n de solicitudes o de tasa en el c\u00f3digo de Rails. Esto crea un riesgo directo de adivinaci\u00f3n de contrase\u00f1as en l\u00ednea:\n- las cuentas de usuario v\u00e1lidas pueden ser atacadas continuamente sin bloqueo temporal\n- la misma debilidad es accesible tanto a trav\u00e9s de \u201c/users/sign_in\u201d como de \u201c/api/v4/auth/login\u201d\n- la adivinaci\u00f3n exitosa produce una cookie de sesi\u00f3n normal en el flujo HTML o un JWT nuevo en el flujo de la API\n- el endpoint de la API es especialmente atractivo para la automatizaci\u00f3n porque no requiere token CSRF\n\nEsto ha sido parcheado en la versi\u00f3n 26.06.08."
          }
        ],
        "id": "CVE-2026-32825",
        "lastModified": "2026-10-24T20:10:00.137",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 7.3,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 2.1,
              "impactScore": 5.2,
              "source": "security-advisories@github.com",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-32825",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-20T18:06:20.638881Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-07-20T17:17:06.140",
        "references": [
          {
            "source": "security-advisories@github.com",
            "url": "https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-736f-cqq3-ccgf"
          }
        ],
        "sourceIdentifier": "security-advisories@github.com",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-307"
              }
            ],
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-32825",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-07-20T18:06:20.638881Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-07-20T17:56:21.076Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "dataCycle-CORE",
              "vendor": "datacycle-engine",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c= 25.07.3"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, the application accepts unlimited password guesses against both the browser login flow and the JSON login endpoint. The source code enables Devise\u0027s `:lockable` module on the user model but explicitly disables both lock and unlock strategies, and no request throttling or rate-limiting layer was identified in the Rails code. This creates a direct online password-guessing risk:\n- valid user accounts can be attacked continuously without temporary lockout\n- the same weakness is reachable through both `/users/sign_in` and `/api/v4/auth/login`\n- successful guessing yields a normal session cookie in the HTML flow or a fresh JWT in the API flow\n- the API endpoint is especially attractive for automation because it requires no CSRF token\n\nThis has been patched in version 26.06.08."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 7.3,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-307",
                  "description": "CWE-307: Improper Restriction of Excessive Authentication Attempts",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-07-20T16:15:37.377Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-736f-cqq3-ccgf",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-736f-cqq3-ccgf"
            }
          ],
          "source": {
            "advisory": "GHSA-736f-cqq3-ccgf",
            "discovery": "UNKNOWN"
          },
          "title": "dataCycle No Brute-Force Protection On Web And API Login Endpoints"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-32825",
        "datePublished": "2026-07-20T16:15:37.377Z",
        "dateReserved": "2026-03-16T17:35:36.697Z",
        "dateUpdated": "2026-07-20T18:06:24.323Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.