PULSE
FEED
ransombarracuda reclama a Dallas Fort Worth Fertility Associates · US · Healthcareransompear reclama a Law Office of Ronald D. Weiss, P.C · US · Professional Servicesransomeclipse reclama a Realta Technologies · IE · Technologyransominception reclama a Lucid Motors · US · Manufacturingransomwhitearmor reclama a DROP 1 — CASANARE, PAJONAL, PUTUMAYO AND URUS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CRED... · CO · Healthcareransompixelleaks reclama a MT5 algo-trading farm (OneFunded funded account, WINSERVER) · Financial Servicesransompixelleaks reclama a bastion.internal domain controller (GCP, GRATEFUL-V1) · Technologyransompixelleaks reclama a Aixia Group AB (Nasdaq-listed AI/IT, Sweden) · SE · Technologyransompixelleaks reclama a Kingsport Cargo (logistics, Laravel intranet) · Transportationransompixelleaks reclama a Arab Software Computer / ASCON (Oracle ERP hosting, Alexandria) · EG · Technologyransommedusalocker reclama a Lee Memorial Health System · US · Healthcareransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcareransombarracuda reclama a Dallas Fort Worth Fertility Associates · US · Healthcareransompear reclama a Law Office of Ronald D. Weiss, P.C · US · Professional Servicesransomeclipse reclama a Realta Technologies · IE · Technologyransominception reclama a Lucid Motors · US · Manufacturingransomwhitearmor reclama a DROP 1 — CASANARE, PAJONAL, PUTUMAYO AND URUS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CRED... · CO · Healthcareransompixelleaks reclama a MT5 algo-trading farm (OneFunded funded account, WINSERVER) · Financial Servicesransompixelleaks reclama a bastion.internal domain controller (GCP, GRATEFUL-V1) · Technologyransompixelleaks reclama a Aixia Group AB (Nasdaq-listed AI/IT, Sweden) · SE · Technologyransompixelleaks reclama a Kingsport Cargo (logistics, Laravel intranet) · Transportationransompixelleaks reclama a Arab Software Computer / ASCON (Oracle ERP hosting, Alexandria) · EG · Technologyransommedusalocker reclama a Lee Memorial Health System · US · Healthcareransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcare
← Todos los CVEs
CVE Watch20 nov 2026

CVE-2026-131170

Our payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status re

CVSS

—

Sin CVSS

EPSS

—

KEV

—

Exploit Today

0

0-100

Publicado: 20 nov 2026 · Última mod.: 20 nov 2026 · CWE-345

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

Our payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users. To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-121714—
—
——0RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl stops at the first body section and preserves the remaining bytes in bare_and_footer without validating message-section order. An authenticated publisher with write permission can place a properties section carrying a forged user-id after the body, causing rabbit_access_control:check_user_id/2 to see no user-id while permissive downstream AMQP 1.0 decoders or AMQP 0-9-1 conversion through classic and quorum queues expose the forged identity. Applications that rely on RabbitMQ-validated user-id metadata can therefore accept attacker-controlled publisher attribution. Strict consumers that reject out-of-order sections are not vulnerable to identity spoofing, and the issue does not bypass broker routing or destination authorization. This issue is fixed in version 4.3.5.19h
CVE-2026-552168.1 ALT
—
——0Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.46.0, social account linking can use an unverified email returned by the standard OAuth 2.0 or Azure AD connector to select an existing local account. When findSocialRelatedUser matches a victim's email and a request to POST /api/experience/identification enables linkSocialIdentity, an attacker who controls that unverified provider email can link an attacker-controlled social identity to the victim account and sign in as the victim. The issue applies when the provider does not verify email ownership or allows the value to be set freely; Google, GitHub, and default OIDC connector behavior is not affected because those paths expose only verified email. Version 1.46.0 adds an opt-in email synchronization control to the standard OAuth 2.0 connector, while the Azure AD connector has offered an equivalent opt-in control since version 1.43.0. These controls preserve existing behavior by default, so administrators must enable them on affected connectors. A configurable mitigation is available in version 1.46.0.21h
CVE-2026-1154096.5 MED
—
——0In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths `github.com/eclipse-keypont/crypto11 <= 1.6.8`, `github.com/ThalesGroup/crypto11 <= 1.7.0-rc1` and `github.com/ThalesIgnite/crypto11 <= 1.2.5`), the key-pair and certificate lookup functions (`FindKeyPair`, `FindKeyPairs`, `FindKeyPairsWithAttributes`, `FindAllKeyPairs`, the `FindRSAKeyPair*` family and `FindAllPairedCertificates`) pair a private key with a public key object, or with a certificate, by `CKA_ID`/`CKA_LABEL` alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's `CKA_ID` and label, and crypto11 may return it as that key's public half. An application that publishes or trusts `Signer.Public()` (a JWKS endpoint, a key registry, `authorized_keys`, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the private key has no `CKA_ID`, pairing a label-only private key with the first public key of its type on the token. The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later.20h
CVE-2026-1326075.3 MED
5.4%
——2Insufficient verification of data authenticity in the decryption component of Amazon S3 Encryption Client for PHP in AWS SDK for PHP before 3.383.1 might allow an authenticated remote user to forge ciphertext that decrypts to arbitrary plaintext via manipulation of the GCM authentication tag length metadata. To remediate this issue, users should upgrade to AWS SDK for PHP version 3.383.1 or later.22h
CVE-2026-1312893.1 BAJ
2.0%
——1In Splunk SOAR versions below 8.8.0, a user who holds a role that can edit and run playbooks in Splunk SOAR could cause Splunk SOAR to run non-read-only actions from a Safe Mode playbook, resulting in unauthorized state changes. The vulnerability is possible because Splunk SOAR does not verify that the playbook run context in an action request matches the context that the server provided.2d
CVE-2026-47278—
21.2%
——6Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3.2d