p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @payloadcms/graphql

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @payloadcms/graphql: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3

  1. CVE-2026-34751

    Kritisch · CVSS 9.1EPSS 0,31%Korrektur verfügbar

    Payload has Unvalidated Input in Password Recovery Endpoints

    Payload is a free and open source headless content management system. Prior to version 3.79.1 in @payloadcms/graphql and payload, a vulnerability in the password recovery flow could allow an unauthenticated attacker to perform actions on behalf of a user who initiates a password reset. This issue has been patched in version 3.79.1 for @payloadcms/graphql and payload.

    • Auf 3.79.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2025-4644

    Mittel · CVSS 5.3EPSS 0,43%Korrektur verfügbar

    User Session Fixation after Account Removal in PayloadCMS

    A Session Fixation vulnerability existed in Payload's SQLite adapter due to identifier reuse during account creation. A malicious attacker could create a new account, save its JSON Web Token (JWT), and then delete the account, which did not invalidate the JWT. As a result, the next newly created user would receive the same identifier, allowing the attacker to reuse the JWT to authenticate and perform actions as that user. This issue has been fixed in version 3.44.0 of Payload.

    • Auf 3.44.0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2025-4643

    Mittel · CVSS 6.3EPSS 0,41%Korrektur verfügbar

    Lack of JWT Expiration after Log Out in PayloadCMS

    Payload uses JSON Web Tokens (JWT) for authentication. After log out JWT is not invalidated, which allows an attacker who has stolen or intercepted token to freely reuse it until expiration date (which is by default set to 2 hours, but can be changed). This issue has been fixed in version 3.44.0 of Payload.

    • Auf 3.44.0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →