FKIE_CVE-2026-45410

Vulnerability from fkie_nvd - Published: 2026-05-28 22:17 - Updated: 2026-07-21 10:10
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Summary
TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18.
References
security-advisories@github.comhttps://gist.github.com/jubnl/c2402adf85d946c1730867aeecc794de
security-advisories@github.comhttps://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r
134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "TREK",
          "vendor": "mauriceboe",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 3.0.18"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14\u00d7 timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18."
    },
    {
      "lang": "es",
      "value": "TREK es un planificador de viajes colaborativo. Antes de la versi\u00f3n 3.0.18, un retorno temprano por usuario inexistente durante el flujo de inicio de sesi\u00f3n permiti\u00f3 a un atacante enumerar cuentas de usuario v\u00e1lidas a trav\u00e9s de una discrepancia en el tiempo de respuesta. Cuando una direcci\u00f3n de correo electr\u00f3nico exist\u00eda en la base de datos, el backend realizaba una comparaci\u00f3n de contrase\u00f1a bcrypt antes de devolver un 401 No autorizado, a\u00f1adiendo ~370 ms de latencia. Cuando el correo electr\u00f3nico no exist\u00eda, el backend devolv\u00eda inmediatamente (~10 ms). Esta diferencia de tiempo de ~14\u00d7 pod\u00eda detectarse sin ninguna diferencia en los c\u00f3digos de estado HTTP o los cuerpos de respuesta. Esta vulnerabilidad est\u00e1 corregida en la versi\u00f3n 3.0.18."
    }
  ],
  "id": "CVE-2026-45410",
  "lastModified": "2026-07-21T10:10:00.103",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-45410",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-05-29T14:46:27.011976Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-05-28T22:17:01.050",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://gist.github.com/jubnl/c2402adf85d946c1730867aeecc794de"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r"
    },
    {
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "url": "https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-203"
        },
        {
          "lang": "en",
          "value": "CWE-208"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.