Common Weakness Enumeration

CWE-345

Weakness Discouraged

Insufficient Verification of Data Authenticity

Abstraction: Class · Status: Draft

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Dimensions

  • Behavior-Type: Verification
  • Behavior-Property: Insufficient
  • Info-Type: Data
  • Info-Property: Authenticity
Mapping guidance

This CWE entry is a level-1 Class (i.e., a child of a Pillar). It might have lower-level children that would be more appropriate

Examine children of this entry to see if there is a better fit

Relationships and members
ChildOf: CWE-693 · View CWE-1000
Modes of introduction
Architecture and Design
Implementation

REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Detection methods

Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Effectiveness: High

Notes

Relationship

"origin validation" could fall under this.

Maintenance

The specific ways in which the origin is not properly identified should be laid out as separate weaknesses. In some sense, this is more like a category.

Content history
Submission: PLOVER · 2006-07-19 · CWE Draft 3
Modification: Eric Dalci · Cigital · 2008-07-01 · CWE 1.0

updated Time_of_Introduction

Modification: CWE Content Team · MITRE · 2008-09-08 · CWE 1.0

updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2009-05-27 · CWE 1.4

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2009-07-27 · CWE 1.5

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2010-02-16 · CWE 1.8

updated Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2010-04-05 · CWE 1.8.1

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2010-12-13 · CWE 1.11

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2011-06-01 · CWE 1.13

updated Common_Consequences

Modification: CWE Content Team · MITRE · 2011-06-27 · CWE 2.0

updated Common_Consequences

Modification: CWE Content Team · MITRE · 2012-05-11 · CWE 2.2

updated References, Related_Attack_Patterns, Relationships

Modification: CWE Content Team · MITRE · 2013-07-17 · CWE 2.5

updated Relationships

Modification: CWE Content Team · MITRE · 2014-07-30 · CWE 2.8

updated Relationships

Modification: CWE Content Team · MITRE · 2015-12-07 · CWE 2.9

updated Relationships

Modification: CWE Content Team · MITRE · 2017-05-03 · CWE 2.11

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2017-11-08 · CWE 3.0

updated Applicable_Platforms, Modes_of_Introduction, Relationships

Modification: CWE Content Team · MITRE · 2019-06-20 · CWE 3.3

updated Related_Attack_Patterns, Relationships

Modification: CWE Content Team · MITRE · 2020-02-24 · CWE 4.0

updated Relationships

Modification: CWE Content Team · MITRE · 2020-06-25 · CWE 4.1

updated Relationships

Modification: CWE Content Team · MITRE · 2020-08-20 · CWE 4.2

updated Relationships

Modification: CWE Content Team · MITRE · 2021-07-20 · CWE 4.5

updated Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2021-10-28 · CWE 4.6

updated Relationships

Modification: CWE Content Team · MITRE · 2023-01-31 · CWE 4.10

updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, References, Related_Attack_Patterns

Modification: CWE Content Team · MITRE · 2023-04-27 · CWE 4.11

updated Detection_Factors, Relationships

Modification: CWE Content Team · MITRE · 2023-06-29 · CWE 4.12

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2024-02-29 · CWE 4.14

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2025-12-11 · CWE 4.19

updated Relationships, Weakness_Ordinalities

Modification: CWE Content Team · MITRE · 2026-10-28 · CWE 5.0

updated Dimensions, References, Relationships, Taxonomy_Mappings

1437 vulnerabilities reference this CWE, most recent first.

CVE-2026-133190 (GCVE-0-2026-133190)

Vulnerability from cvelistv5 – Published: 2026-11-19 14:44 – Updated: 2026-11-19 14:52
VLAI
Title
MISP CryptographicKey: Revoked PGP Keys Still Validate Protected Event Signatures and Key Revocation Sync Is Ineffective
Summary
MISP, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events. Two related defects allow a revoked PGP key to remain effective for signing and validating protected events. First, the validateProtectedEvent() method in the CryptographicKey model iterates over the event's stored cryptographic keys to verify a PGP signature but does not check the revoked flag on each key. A key explicitly marked as revoked is still used to validate signatures, meaning an entity whose key has been revoked can continue to sign protected events and have them accepted by the MISP instance. Second, the captureCryptographicKeyUpdate() method, responsible for synchronizing the key list when a sync user edits a protected event, contained a query bug (find('first') instead of find('all')) that caused only the first stored key to be considered. As a result, revocations of additional keys were never persisted, keys absent from the pushed list were not removed, and entries lacking an explicit fingerprint were mismatched and incorrectly deleted. Additionally, the revocation logic did not enforce the invariant that a revocation, once stored, is never lifted by subsequent pushes. A third minor issue: a signed protected event submitted without any cryptographic keys triggered an unhandled 500 error rather than a proper rejection response. Preconditions: the attacker must be an authenticated sync user with permission to add or edit protected events on the MISP instance. The impact is that revoked keys retain signing authority, key revocations propagated by sync partners are silently dropped, and the integrity of the protected-event trust chain is compromised. In a multi-instance MISP deployment, events signed by revoked keys can propagate to other instances, extending the integrity impact across the sync network.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-19 14:35 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 14:52 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
  • CWE-287 - Improper Authentication
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version
misp misp Affected: 0 , ≤ 2.5.51 (semver)
    cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-19 14:35
Model
qwen3.8:27b
Input
https://github.com/MISP/MISP/commit/eee1f8b67.patch ad525a5a8146…
Confidence
medium
Commit Subject Patch SHA-256
eee1f8b675c5 fix: [security] Revoked keys no longer sign protected events, ad525a5a8146…
Fix summary

The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500.

Patch summary

In CryptographicKey.php: (1) validateProtectedEvent() now checks $supplied_key['revoked'] and continues (skips) if set, before calling verifySignature(). (2) captureCryptographicKeyUpdate() changes find('first') to find('all') so all stored keys are considered. (3) A pre-loop computes a fingerprint via extractKeyData() for pushed entries that lack one. (4) The revocation branch is restructured: it now saves only the revoked flag (id + revoked=1) and the condition uses !empty() checks to ensure a revocation is never lifted. (5) The $existingKey array access is flattened (removing the nested 'CryptographicKey' key). (6) deleteAll() is guarded with an empty check on $toRemove. (7) The no-keys error message includes the event UUID and the log entry uses event ID 0. In tests/testregressions.py: a new ProtectedEventKeyRevocation test class adds nine regression tests covering revoked-key rejection, unrevoked-key acceptance, revocation persistence, non-lifting of revocations, key removal, fingerprint-less entry match

CVSS rationale

AV:N: MISP is a network-accessible web application; the attacker interacts via the HTTP API. AC:L: exploitation requires only signing an event with a revoked key and submitting it; no race conditions or special timing. AT:N: no special targeting beyond network reachability to the MISP instance. PR:L: the attacker must be an authenticated sync user with permission to add/edit protected events. UI:N: no victim interaction is required. VC:N: no confidentiality impact is evident. VI:H: integrity is significantly impacted because revoked keys retain signing authority and revocations are not applied, undermining the trust chain for protected events. VA:N: the 500-error issue is minor and does not constitute a meaningful availability impact. SC:N: no secondary confidentiality impact. SI:H: in a multi-instance MISP sync network, events signed by revoked keys can propagate to peer instances, extending the integrity compromise. SA:N: no secondary availability impact.

Weakness rationale
  • CWE-345 The signature verification routine validated the cryptographic signature but failed to verify the authenticity/validity of the signing key by checking its revocation status. A revoked key was treated as a valid signing authority, which is a failure to fully verify data authenticity.
  • CWE-287 The system accepted a revoked key as a valid credential for signing protected events, effectively failing to authenticate the signer's current authorization status. The key revocation mechanism was bypassed.
Attack pattern rationale
  • CAPEC-124 The revoked-key state is an exceptional condition in the key lifecycle that the application failed to handle correctly during signature validation and key synchronization. The attacker exploits the system's failure to treat a revoked key as an exceptional (invalid) state. This is the closest CAPEC pattern; a more specific 'key revocation bypass' pattern does not exist in the CAPEC catalog, so CAPEC-124 is the best available match.
  • CAPEC-100 The key-sync path is vulnerable to manipulation of the pushed key list: by omitting keys or crafting entries without fingerprints, an attacker can prevent revocations from being applied or cause valid keys to be removed. This is a secondary attack vector enabled by the same code defects. The mapping is approximate because the primary issue is a logic flaw rather than direct parameter injection.
Assumptions to verify
  • The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
  • The attacker is assumed to be an authenticated sync user with permission to add or edit protected events; unauthenticated exploitation is not evidenced.
  • The secondary integrity impact (SI:H) assumes a multi-instance MISP sync deployment; in a single-instance deployment the secondary impact may be lower.
  • CAPEC-124 is selected as the closest available pattern; no CAPEC specifically covers cryptographic key revocation bypass, so the mapping is approximate.
  • The Co-Authored-By line for Claude Opus 5.5 is treated as a tool credit; it is unclear whether this represents AI-assisted development or a placeholder.
  • The 500-error issue (signed event without keys) is treated as a minor robustness defect subsumed under the primary revocation-bypass vulnerability rather than a separate issue.
  • CVSS AT:N is used because the only options are N or P; the attacker does perform active interaction (submitting a signed event), but no special passive observation position is required.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 5 11 medium 7
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-14 11:53 UTC Fix developed Corrective change authored (eee1f8b675c5c472fa73b41982824c0c17dd639e): fix: [security] Revoked keys no longer sign protected events, https://github.com/MISP/MISP/commit/eee1f8b67.patch
  2. 2026-11-19 14:34 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/eee1f8b67.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133190",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T14:52:11.814868Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T14:52:25.872Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "CryptographicKey model (app/Model/CryptographicKey.php)"
          ],
          "product": "misp",
          "programFiles": [
            "app/Model/CryptographicKey.php"
          ],
          "repo": "https://github.com/MISP/MISP",
          "vendor": "misp",
          "versions": [
            {
              "lessThanOrEqual": "2.5.51",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "2.5.51",
                  "versionStartIncluding": "0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "iglocska"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "ENISA"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "CERT.pl"
        },
        {
          "lang": "en",
          "type": "tool",
          "value": "Claude Opus 5.5"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "MISP, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events. Two related defects allow a revoked PGP key to remain effective for signing and validating protected events.\n\nFirst, the validateProtectedEvent() method in the CryptographicKey model iterates over the event\u0027s stored cryptographic keys to verify a PGP signature but does not check the revoked flag on each key. A key explicitly marked as revoked is still used to validate signatures, meaning an entity whose key has been revoked can continue to sign protected events and have them accepted by the MISP instance.\n\nSecond, the captureCryptographicKeyUpdate() method, responsible for synchronizing the key list when a sync user edits a protected event, contained a query bug (find(\u0027first\u0027) instead of find(\u0027all\u0027)) that caused only the first stored key to be considered. As a result, revocations of additional keys were never persisted, keys absent from the pushed list were not removed, and entries lacking an explicit fingerprint were mismatched and incorrectly deleted. Additionally, the revocation logic did not enforce the invariant that a revocation, once stored, is never lifted by subsequent pushes.\n\nA third minor issue: a signed protected event submitted without any cryptographic keys triggered an unhandled 500 error rather than a proper rejection response.\n\nPreconditions: the attacker must be an authenticated sync user with permission to add or edit protected events on the MISP instance. The impact is that revoked keys retain signing authority, key revocations propagated by sync partners are silently dropped, and the integrity of the protected-event trust chain is compromised. In a multi-instance MISP deployment, events signed by revoked keys can propagate to other instances, extending the integrity impact across the sync network."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-124",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-124 Exploiting Incorrectly Handled Exceptional Conditions"
            }
          ]
        },
        {
          "capecId": "CAPEC-100",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-100 Parameter Tampering"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 3.7,
            "baseSeverity": "LOW",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-19T14:35:26Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345 Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287 Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T14:44:46.132Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/eee1f8b67"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500."
        }
      ],
      "title": "MISP CryptographicKey: Revoked PGP Keys Still Validate Protected Event Signatures and Key Revocation Sync Is Ineffective",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.",
                  "The attacker is assumed to be an authenticated sync user with permission to add or edit protected events; unauthenticated exploitation is not evidenced.",
                  "The secondary integrity impact (SI:H) assumes a multi-instance MISP sync deployment; in a single-instance deployment the secondary impact may be lower.",
                  "CAPEC-124 is selected as the closest available pattern; no CAPEC specifically covers cryptographic key revocation bypass, so the mapping is approximate.",
                  "The Co-Authored-By line for Claude Opus 5.5 is treated as a tool credit; it is unclear whether this represents AI-assisted development or a placeholder.",
                  "The 500-error issue (signed event without keys) is treated as a minor robustness defect subsumed under the primary revocation-bypass vulnerability rather than a separate issue.",
                  "CVSS AT:N is used because the only options are N or P; the attacker does perform active interaction (submitting a signed event), but no special passive observation position is required."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-124",
                    "rationale": "The revoked-key state is an exceptional condition in the key lifecycle that the application failed to handle correctly during signature validation and key synchronization. The attacker exploits the system\u0027s failure to treat a revoked key as an exceptional (invalid) state. This is the closest CAPEC pattern; a more specific \u0027key revocation bypass\u0027 pattern does not exist in the CAPEC catalog, so CAPEC-124 is the best available match."
                  },
                  {
                    "capecId": "CAPEC-100",
                    "rationale": "The key-sync path is vulnerable to manipulation of the pushed key list: by omitting keys or crafting entries without fingerprints, an attacker can prevent revocations from being applied or cause valid keys to be removed. This is a secondary attack vector enabled by the same code defects. The mapping is approximate because the primary issue is a logic flaw rather than direct parameter injection."
                  }
                ],
                "commit": "eee1f8b675c5c472fa73b41982824c0c17dd639e",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA and CERT.pl"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "iglocska"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  },
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA"
                  },
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "CERT.pl"
                  },
                  {
                    "lang": "en",
                    "type": "tool",
                    "value": "Claude Opus 5.5"
                  }
                ],
                "cvssRationale": "AV:N: MISP is a network-accessible web application; the attacker interacts via the HTTP API. AC:L: exploitation requires only signing an event with a revoked key and submitting it; no race conditions or special timing. AT:N: no special targeting beyond network reachability to the MISP instance. PR:L: the attacker must be an authenticated sync user with permission to add/edit protected events. UI:N: no victim interaction is required. VC:N: no confidentiality impact is evident. VI:H: integrity is significantly impacted because revoked keys retain signing authority and revocations are not applied, undermining the trust chain for protected events. VA:N: the 500-error issue is minor and does not constitute a meaningful availability impact. SC:N: no secondary confidentiality impact. SI:H: in a multi-instance MISP sync network, events signed by revoked keys can propagate to peer instances, extending the integrity compromise. SA:N: no secondary availability impact.",
                "draft": false,
                "fixSummary": "The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500.",
                "generatedAt": "2026-11-19T14:35:26.990914Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 7,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 5
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "ad525a5a81462a3936cd6ad7cb153b93b23ec465ba010b8634cee54bcb6c7d87",
                "patchSummary": "In CryptographicKey.php: (1) validateProtectedEvent() now checks $supplied_key[\u0027revoked\u0027] and continues (skips) if set, before calling verifySignature(). (2) captureCryptographicKeyUpdate() changes find(\u0027first\u0027) to find(\u0027all\u0027) so all stored keys are considered. (3) A pre-loop computes a fingerprint via extractKeyData() for pushed entries that lack one. (4) The revocation branch is restructured: it now saves only the revoked flag (id + revoked=1) and the condition uses !empty() checks to ensure a revocation is never lifted. (5) The $existingKey array access is flattened (removing the nested \u0027CryptographicKey\u0027 key). (6) deleteAll() is guarded with an empty check on $toRemove. (7) The no-keys error message includes the event UUID and the log entry uses event ID 0. In tests/testregressions.py: a new ProtectedEventKeyRevocation test class adds nine regression tests covering revoked-key rejection, unrevoked-key acceptance, revocation persistence, non-lifting of revocations, key removal, fingerprint-less entry match",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "eee1f8b675c5c472fa73b41982824c0c17dd639e",
                    "date": "Sat, 14 Nov 2026 12:53:39 +0100",
                    "patchSha256": "ad525a5a81462a3936cd6ad7cb153b93b23ec465ba010b8634cee54bcb6c7d87",
                    "retrievedAt": "2026-11-19T14:34:41.330303Z",
                    "source": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
                    "sourceUrl": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
                    "subject": "fix: [security] Revoked keys no longer sign protected events,"
                  }
                ],
                "source": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-19T14:35:26Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Revoked keys no longer sign protected events,",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-345",
                    "rationale": "The signature verification routine validated the cryptographic signature but failed to verify the authenticity/validity of the signing key by checking its revocation status. A revoked key was treated as a valid signing authority, which is a failure to fully verify data authenticity."
                  },
                  {
                    "cweId": "CWE-287",
                    "rationale": "The system accepted a revoked key as a valid credential for signing protected events, effectively failing to authenticate the signer\u0027s current authorization status. The key revocation mechanism was bypassed."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (eee1f8b675c5c472fa73b41982824c0c17dd639e): fix: [security] Revoked keys no longer sign protected events,",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/eee1f8b67.patch"
                    ],
                    "timestamp": "2026-11-14T11:53:39Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/eee1f8b67.patch"
                    ],
                    "timestamp": "2026-11-19T14:34:41.330303Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20236"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133190",
    "datePublished": "2026-11-19T14:44:46.132Z",
    "dateReserved": "2026-11-19T14:44:40.990Z",
    "dateUpdated": "2026-11-19T14:52:25.872Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-133188 (GCVE-0-2026-133188)

Vulnerability from cvelistv5 – Published: 2026-11-19 14:32 – Updated: 2026-11-19 20:09
VLAI
Title
MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers
Summary
MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace("/\s+/", "", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic. The vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide. The fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster 'meta' keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-19 14:26 UTC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 20:08 UTC
CWE
  • CWE-347 - Improper Verification of Cryptographic Signature
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
Impacted products
Vendor Product Version
misp misp Affected: 0 , ≤ 2.5.51 (semver)
    cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-19 14:26
Model
qwen3.8:27b
Input
patch set (2 sources) b81058778949…
Confidence
medium
Commit Subject Patch SHA-256
d5a3e9900708 fix: [security] Protected events refuse signed data with bd22e66a2c32…
18d0e9a77d0c fix: [security] Protected events are signed over their exact 4340f1f4d2e8…
Fix summary

The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks.

Patch summary

Patch 1 (d5a3e9900) adds a private method __hasUnsignedWhitespace() to CryptographicKey that recursively scans decoded JSON for whitespace in string keys (excluding 'meta' sub-keys) and in values whose keys match identifier patterns (uuid, id, timestamp, distribution, date). validateProtectedEvent() now calls this check after a successful signature verification and returns false with a log entry if unsigned whitespace is found. Patch 2 (18d0e9a77) extends signWithInstanceKey() and verifySignature() with an $exact parameter that skips whitespace stripping. A new signatureHeaders() method selects the appropriate signature header(s) based on the peer's MISP version. EventsController, ServerSyncTool, and RestResponseComponent are updated to emit and consume the x-pgp-signature-v2 header. The signature_version field is injected into protected event bodies. Server.php passes the v2 header to validateProtectedEvent(). A new test file ProtectedEventExactSignatureTest.php (339 lines) covers acceptance, rejection, and

CVSS rationale

AV:N: The attacker operates over the network, intercepting and modifying traffic between MISP instances. AC:L: Inserting whitespace characters into JSON is a simple, deterministic transformation requiring no special conditions. AT:N: The target does not need to be in a particular state; any protected event in transit is vulnerable. PR:N: The attacker does not require authentication to the MISP instance; a network relay position suffices. UI:N: No user interaction is required; the tampered event is processed automatically. VC:N: No confidentiality impact; the attack modifies data, not exposes it. VI:H: The attacker can rename JSON fields and alter identifier values (UUIDs, timestamps), changing the semantic meaning of protected events while the signature still validates. VA:N: No availability impact. SC:N, SI:N, SA:N: The impact is confined to the receiving MISP instance's data integrity; no cross-scope or availability effects are evidenced.

Weakness rationale
  • CWE-347 The PGP signature was computed and verified over a whitespace-stripped representation of the JSON body rather than the exact bytes transmitted. This allowed an attacker to modify the data (by inserting whitespace into keys or identifiers) without invalidating the signature, constituting an improper verification of the cryptographic signature's coverage.
  • CWE-345 The signature verification mechanism did not fully ensure the authenticity of the received data because the normalization step (whitespace removal) created a gap between the signed representation and the actual data, allowing undetected modifications.
Attack pattern rationale
  • CAPEC-126 The digital signature mechanism was implemented over a normalized (whitespace-stripped) representation of the data rather than the exact transmitted bytes. An attacker in a relay position exploits this by inserting whitespace into JSON keys or identifier values, which survives the normalization and thus the signature check. CAPEC-126 is the closest match; uncertainty exists because the CAPEC catalog does not have a more specific pattern for signature-coverage gaps introduced by data normalization.
Assumptions to verify
  • The CAPEC-126 mapping is the closest available pattern; the CAPEC catalog lacks a more specific entry for signature-coverage gaps introduced by data normalization before signing.
  • CVSS PR:N assumes the attacker only needs a network relay position and does not require authentication to either MISP instance; if the deployment requires authenticated relay, PR would be elevated.
  • CVSS VI:H assumes that renaming JSON fields or altering timestamps in protected events constitutes a high integrity impact; if the specific deployment treats these fields as non-critical, VI could be L.
  • The affected version boundary (< 3.0.0) is inferred from the patch's version_compare logic; the exact last affected release is not stated in the patch.
  • The Galaxy cluster 'meta' key exclusion from the whitespace scan means whitespace in meta keys remains a residual (documented) limitation, not a vulnerability.
  • SSVC technical_impact is set to 'partial' as the attacker can only insert whitespace, not arbitrarily rewrite event content; if field renaming has critical downstream effects in a specific deployment, 'total' may be more appropriate.
  • The Co-Authored-By line credits an AI assistant (Claude Opus 5.5); inclusion as a remediation developer follows the explicit metadata but is atypical for CVE credit conventions.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 5 11 medium 7
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-13 11:25 UTC Fix developed Corrective change authored (d5a3e9900708e409bc9c517c57aa819883ca879e): fix: [security] Protected events refuse signed data with https://github.com/MISP/MISP/commit/d5a3e9900.patch
  2. 2026-11-17 13:37 UTC Fix developed Corrective change authored (18d0e9a77d0c1d790a1742d9d886bf033d303ac6): fix: [security] Protected events are signed over their exact https://github.com/MISP/MISP/commit/18d0e9a77.patch
  3. 2026-11-19 14:25 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/d5a3e9900.patch
  4. 2026-11-19 14:25 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/18d0e9a77.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133188",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T20:08:55.828367Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T20:09:05.870Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/Model/CryptographicKey.php",
            "app/Controller/EventsController.php",
            "app/Lib/Tools/ServerSyncTool.php",
            "app/Model/Server.php",
            "app/Controller/Component/RestResponseComponent.php"
          ],
          "product": "misp",
          "programFiles": [],
          "repo": "https://github.com/MISP/MISP",
          "vendor": "misp",
          "versions": [
            {
              "lessThanOrEqual": "2.5.51",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "2.5.51",
                  "versionStartIncluding": "0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "ENISA"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "iglocska"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace(\"/\\s+/\", \"\", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic.\n\nThe vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide.\n\nThe fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster \u0027meta\u0027 keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-126",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-126 Exploiting Incorrectly Implemented Digital Signatures"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 6.9,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-19T14:26:06Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-347",
              "description": "CWE-347 Improper Verification of Cryptographic Signature",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345 Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T14:32:35.724Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/d5a3e9900"
        },
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/18d0e9a77"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks."
        }
      ],
      "title": "MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The CAPEC-126 mapping is the closest available pattern; the CAPEC catalog lacks a more specific entry for signature-coverage gaps introduced by data normalization before signing.",
                  "CVSS PR:N assumes the attacker only needs a network relay position and does not require authentication to either MISP instance; if the deployment requires authenticated relay, PR would be elevated.",
                  "CVSS VI:H assumes that renaming JSON fields or altering timestamps in protected events constitutes a high integrity impact; if the specific deployment treats these fields as non-critical, VI could be L.",
                  "The affected version boundary (\u003c 3.0.0) is inferred from the patch\u0027s version_compare logic; the exact last affected release is not stated in the patch.",
                  "The Galaxy cluster \u0027meta\u0027 key exclusion from the whitespace scan means whitespace in meta keys remains a residual (documented) limitation, not a vulnerability.",
                  "SSVC technical_impact is set to \u0027partial\u0027 as the attacker can only insert whitespace, not arbitrarily rewrite event content; if field renaming has critical downstream effects in a specific deployment, \u0027total\u0027 may be more appropriate.",
                  "The Co-Authored-By line credits an AI assistant (Claude Opus 5.5); inclusion as a remediation developer follows the explicit metadata but is atypical for CVE credit conventions."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-126",
                    "rationale": "The digital signature mechanism was implemented over a normalized (whitespace-stripped) representation of the data rather than the exact transmitted bytes. An attacker in a relay position exploits this by inserting whitespace into JSON keys or identifier values, which survives the normalization and thus the signature check. CAPEC-126 is the closest match; uncertainty exists because the CAPEC catalog does not have a more specific pattern for signature-coverage gaps introduced by data normalization."
                  }
                ],
                "commit": "18d0e9a77d0c1d790a1742d9d886bf033d303ac6",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "iglocska"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  }
                ],
                "cvssRationale": "AV:N: The attacker operates over the network, intercepting and modifying traffic between MISP instances. AC:L: Inserting whitespace characters into JSON is a simple, deterministic transformation requiring no special conditions. AT:N: The target does not need to be in a particular state; any protected event in transit is vulnerable. PR:N: The attacker does not require authentication to the MISP instance; a network relay position suffices. UI:N: No user interaction is required; the tampered event is processed automatically. VC:N: No confidentiality impact; the attack modifies data, not exposes it. VI:H: The attacker can rename JSON fields and alter identifier values (UUIDs, timestamps), changing the semantic meaning of protected events while the signature still validates. VA:N: No availability impact. SC:N, SI:N, SA:N: The impact is confined to the receiving MISP instance\u0027s data integrity; no cross-scope or availability effects are evidenced.",
                "draft": false,
                "fixSummary": "The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks.",
                "generatedAt": "2026-11-19T14:26:06.814235Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 7,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 5
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "b81058778949ad6e64fefc78c4a9806e7776068075a40a338d47eb1d26eafde6",
                "patchSummary": "Patch 1 (d5a3e9900) adds a private method __hasUnsignedWhitespace() to CryptographicKey that recursively scans decoded JSON for whitespace in string keys (excluding \u0027meta\u0027 sub-keys) and in values whose keys match identifier patterns (uuid, id, timestamp, distribution, date). validateProtectedEvent() now calls this check after a successful signature verification and returns false with a log entry if unsigned whitespace is found.\n\nPatch 2 (18d0e9a77) extends signWithInstanceKey() and verifySignature() with an $exact parameter that skips whitespace stripping. A new signatureHeaders() method selects the appropriate signature header(s) based on the peer\u0027s MISP version. EventsController, ServerSyncTool, and RestResponseComponent are updated to emit and consume the x-pgp-signature-v2 header. The signature_version field is injected into protected event bodies. Server.php passes the v2 header to validateProtectedEvent(). A new test file ProtectedEventExactSignatureTest.php (339 lines) covers acceptance, rejection, and",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "d5a3e9900708e409bc9c517c57aa819883ca879e",
                    "date": "Fri, 13 Nov 2026 12:25:34 +0100",
                    "patchSha256": "bd22e66a2c3212896f9b0c25657a4e3d2e47ff2ba6bd377d33b4b62b2c524e08",
                    "retrievedAt": "2026-11-19T14:25:13.678489Z",
                    "source": "https://github.com/MISP/MISP/commit/d5a3e9900.patch",
                    "sourceUrl": "https://github.com/MISP/MISP/commit/d5a3e9900.patch",
                    "subject": "fix: [security] Protected events refuse signed data with"
                  },
                  {
                    "commit": "18d0e9a77d0c1d790a1742d9d886bf033d303ac6",
                    "date": "Tue, 17 Nov 2026 14:37:58 +0100",
                    "patchSha256": "4340f1f4d2e8a9f0806650a0896c11c11533e3d6ec6df786707ecdf2fd8120a5",
                    "retrievedAt": "2026-11-19T14:25:13.961710Z",
                    "source": "https://github.com/MISP/MISP/commit/18d0e9a77.patch",
                    "sourceUrl": "https://github.com/MISP/MISP/commit/18d0e9a77.patch",
                    "subject": "fix: [security] Protected events are signed over their exact"
                  }
                ],
                "source": "patch set (2 sources)",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-19T14:26:06Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Protected events are signed over their exact",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-347",
                    "rationale": "The PGP signature was computed and verified over a whitespace-stripped representation of the JSON body rather than the exact bytes transmitted. This allowed an attacker to modify the data (by inserting whitespace into keys or identifiers) without invalidating the signature, constituting an improper verification of the cryptographic signature\u0027s coverage."
                  },
                  {
                    "cweId": "CWE-345",
                    "rationale": "The signature verification mechanism did not fully ensure the authenticity of the received data because the normalization step (whitespace removal) created a gap between the signed representation and the actual data, allowing undetected modifications."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (d5a3e9900708e409bc9c517c57aa819883ca879e): fix: [security] Protected events refuse signed data with",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/d5a3e9900.patch"
                    ],
                    "timestamp": "2026-11-13T11:25:34Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Corrective change authored (18d0e9a77d0c1d790a1742d9d886bf033d303ac6): fix: [security] Protected events are signed over their exact",
                    "id": "evt-fix-developed-2",
                    "references": [
                      "https://github.com/MISP/MISP/commit/18d0e9a77.patch"
                    ],
                    "timestamp": "2026-11-17T13:37:58Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/d5a3e9900.patch"
                    ],
                    "timestamp": "2026-11-19T14:25:13.678489Z",
                    "type": "fix-available"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-2",
                    "references": [
                      "https://github.com/MISP/MISP/commit/18d0e9a77.patch"
                    ],
                    "timestamp": "2026-11-19T14:25:13.961710Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20342"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133188",
    "datePublished": "2026-11-19T14:32:35.724Z",
    "dateReserved": "2026-11-19T14:32:32.740Z",
    "dateUpdated": "2026-11-19T20:09:05.870Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-132607 (GCVE-0-2026-132607)

Vulnerability from cvelistv5 – Published: 2026-11-19 21:03 – Updated: 2026-11-20 17:03
VLAI
Title
GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP
Summary
Insufficient 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.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 17:03 UTC
CWE
  • CWE-345 - Insufficient verification of data authenticity
Assigner
AMZN CNA under the mitre root
CNA scorecard A 94/100 over 170 records in the last 180 days details
Impacted products
Vendor Product Version
AWS aws-sdk-php Affected: 3.148.0 , < 3.383.1 (custom)
    cpe:2.3:a:aws:aws-sdk-php:*:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-132607",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T17:03:04.318492Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T17:03:17.262Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "aws-sdk-php",
          "vendor": "AWS",
          "versions": [
            {
              "lessThan": "3.383.1",
              "status": "affected",
              "version": "3.148.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:aws:aws-sdk-php:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "3.383.1",
                  "versionStartIncluding": "3.148.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "OR"
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "[research organization or researcher name]"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eInsufficient 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.\u003c/p\u003e\u003cp\u003eTo remediate this issue, users should upgrade to AWS SDK for PHP version 3.383.1 or later.\u003c/p\u003e"
            }
          ],
          "value": "Insufficient 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.\n\n\n\nTo remediate this issue, users should upgrade to AWS SDK for PHP version 3.383.1 or later."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-148",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-148 Content Spoofing"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6,
            "baseSeverity": "MEDIUM",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "HIGH",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345 Insufficient verification of data authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T21:15:25.911Z",
        "orgId": "ff89ba41-3aa1-4d27-914a-91399e9639e5",
        "shortName": "AMZN"
      },
      "references": [
        {
          "tags": [
            "release-notes",
            "patch"
          ],
          "url": "https://github.com/aws/aws-sdk-php/releases/tag/3.383.1"
        },
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://aws.amazon.com/security/security-bulletins/2026-191-aws/"
        },
        {
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://github.com/aws/aws-sdk-php/security/advisories/GHSA-9c62-hqw2-gj46"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP",
      "x_generator": {
        "engine": "Vulnogram 0.5.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ff89ba41-3aa1-4d27-914a-91399e9639e5",
    "assignerShortName": "AMZN",
    "cveId": "CVE-2026-132607",
    "datePublished": "2026-11-19T21:03:48.443Z",
    "dateReserved": "2026-11-18T19:26:27.465Z",
    "dateUpdated": "2026-11-20T17:03:17.262Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-131289 (GCVE-0-2026-131289)

Vulnerability from cvelistv5 – Published: 2026-11-19 19:56 – Updated: 2026-11-19 20:36
VLAI
Title
Improper Validation through Playbook Safe Mode in Splunk SOAR
Summary
In 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.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 20:25 UTC
CWE
  • CWE-345 - The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Assigner
cisco CNA under the mitre root
CNA scorecard C 67/100 over 580 records in the last 180 days details
Impacted products
Vendor Product Version
Splunk Splunk SOAR Affected: 0 , < 8.8.0 (custom)
Create a notification for this product.
Date Public
2026-11-18 00:00
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-131289",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T20:25:58.292913Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T20:36:45.105Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Splunk SOAR",
          "vendor": "Splunk",
          "versions": [
            {
              "lessThan": "8.8.0",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "datePublic": "2026-11-18T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "In 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.\nThe 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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 3.1,
            "baseSeverity": "LOW",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.",
              "lang": "en",
              "type": "cwe"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T19:56:37.265Z",
        "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "shortName": "cisco"
      },
      "references": [
        {
          "url": "https://advisory.splunk.com/advisories/SVD-2026-1108"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade Splunk SOAR to version 8.8.0 or higher."
        }
      ],
      "source": {
        "advisory": "SVD-2026-1108",
        "discovery": ""
      },
      "title": "Improper Validation through Playbook Safe Mode in Splunk SOAR"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
    "assignerShortName": "cisco",
    "cveId": "CVE-2026-131289",
    "datePublished": "2026-11-19T19:56:37.265Z",
    "dateReserved": "2026-11-17T20:26:14.311Z",
    "dateUpdated": "2026-11-19T20:36:45.105Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129297 (GCVE-0-2026-129297)

Vulnerability from cvelistv5 – Published: 2026-11-16 17:39 – Updated: 2026-11-16 17:54
VLAI
Title
mail-parser: Sender IP address spoofing in `get_server_ipaddress()
Summary
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, get_server_ipaddress() can select an attacker-controlled address from attacker-controlled Received headers. The minimum mechanism needed to distinguish this spoofing issue, derived from the advisory's remediation analysis and verified fix evidence, is appearance-based candidate selection that can treat bracketed IPv4 or IPv6 addresses or HELO markers in sender-written text as MTA-recorded addresses and can continue past a trusted hop that names no address. Applications that rely on the returned value can attribute a message to an attacker-selected sender IP address. This issue is fixed in version 4.6.2.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 17:54 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 8155 records in the last 180 days details
Impacted products
Vendor Product Version
SpamScope mail-parser Affected: < 4.6.2
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-129297",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T17:54:23.374832Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T17:54:38.586Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "mail-parser",
          "vendor": "SpamScope",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 4.6.2"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, get_server_ipaddress() can select an attacker-controlled address from attacker-controlled Received headers. The minimum mechanism needed to distinguish this spoofing issue, derived from the advisory\u0027s remediation analysis and verified fix evidence, is appearance-based candidate selection that can treat bracketed IPv4 or IPv6 addresses or HELO markers in sender-written text as MTA-recorded addresses and can continue past a trusted hop that names no address. Applications that rely on the returned value can attribute a message to an attacker-selected sender IP address. This issue is fixed in version 4.6.2."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345: Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-16T17:39:47.311Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/SpamScope/mail-parser/security/advisories/GHSA-72px-j8gh-p79x",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/SpamScope/mail-parser/security/advisories/GHSA-72px-j8gh-p79x"
        },
        {
          "name": "https://github.com/SpamScope/mail-parser/pull/167",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SpamScope/mail-parser/pull/167"
        },
        {
          "name": "https://github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96"
        },
        {
          "name": "https://github.com/SpamScope/mail-parser/releases/tag/4.6.2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SpamScope/mail-parser/releases/tag/4.6.2"
        }
      ],
      "source": {
        "advisory": "GHSA-72px-j8gh-p79x",
        "discovery": "UNKNOWN"
      },
      "title": "mail-parser: Sender IP address spoofing in `get_server_ipaddress()"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-129297",
    "datePublished": "2026-11-16T17:39:47.311Z",
    "dateReserved": "2026-11-13T22:30:18.284Z",
    "dateUpdated": "2026-11-16T17:54:38.586Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129258 (GCVE-0-2026-129258)

Vulnerability from cvelistv5 – Published: 2026-11-14 14:30 – Updated: 2026-11-16 15:37
VLAI
Title
Tenda AC18 Firmware Upgrade upgrade data authenticity
Summary
A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/upgrade of the component Firmware Upgrade Handler. Such manipulation of the argument upgradeFile leads to insufficient verification of data authenticity. The attack may be launched remotely. The exploit is publicly available and might be used.
SSVC
Exploitation: poc Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 15:12 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
VulDB CNA under the mitre root
CNA scorecard B 83/100 over 3776 records in the last 180 days details
References
URL Tags
https://vuldb.com/vuln/437295 vdb-entrytechnical-description
https://vuldb.com/vuln/437295/cti signaturepermissions-required
https://vuldb.com/cve/CVE-2026-129258 third-party-advisory
https://vuldb.com/submit/1043033 third-party-advisory
https://github.com/longqx223/Tenda-ac-18-V15.03.0… exploitpatch
https://www.tenda.com.cn/ product
Impacted products
Vendor Product Version
Tenda AC18 Affected: 15.03.05.05_multi
Affected: 15.03.05.19 Build 6318
    cpe:2.3:o:tenda:ac18_firmware:*:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-129258",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T15:12:58.266813Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T15:37:49.793Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:o:tenda:ac18_firmware:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "Firmware Upgrade Handler"
          ],
          "product": "AC18",
          "vendor": "Tenda",
          "versions": [
            {
              "status": "affected",
              "version": "15.03.05.05_multi"
            },
            {
              "status": "affected",
              "version": "15.03.05.19 Build 6318"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Longqxxixi (VulDB User)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/upgrade of the component Firmware Upgrade Handler. Such manipulation of the argument upgradeFile leads to insufficient verification of data authenticity. The attack may be launched remotely. The exploit is publicly available and might be used."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "baseScore": 9.4,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P",
            "version": "4.0"
          }
        },
        {
          "cvssV3_1": {
            "baseScore": 9.1,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C",
            "version": "3.1"
          }
        },
        {
          "cvssV3_0": {
            "baseScore": 9.1,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C",
            "version": "3.0"
          }
        },
        {
          "cvssV2_0": {
            "baseScore": 8.3,
            "vectorString": "AV:N/AC:L/Au:M/C:C/I:C/A:C/E:POC/RL:ND/RC:C",
            "version": "2.0"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-14T14:30:22.937Z",
        "orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
        "shortName": "VulDB"
      },
      "references": [
        {
          "name": "VDB-437295 | Tenda AC18 Firmware Upgrade upgrade data authenticity",
          "tags": [
            "vdb-entry",
            "technical-description"
          ],
          "url": "https://vuldb.com/vuln/437295"
        },
        {
          "name": "VDB-437295 | CTI Indicators (IOB, IOC, IOA)",
          "tags": [
            "signature",
            "permissions-required"
          ],
          "url": "https://vuldb.com/vuln/437295/cti"
        },
        {
          "name": "CVE-2026-129258 | CVE Analysis and Report",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/cve/CVE-2026-129258"
        },
        {
          "name": "Submit #1043033 | Tenda AC18 (AC18V1.0BR) wireless router V15.03.05.05_multi ,V15.03.05.19 build 6318  Insufficient Verification of Data Authenticity",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/submit/1043033"
        },
        {
          "tags": [
            "exploit",
            "patch"
          ],
          "url": "https://github.com/longqx223/Tenda-ac-18-V15.03.05.05-/blob/main/2026-10-19-Tenda-AC18-unsigned-firmware-update-advisory-EN.pdf"
        },
        {
          "tags": [
            "product"
          ],
          "url": "https://www.tenda.com.cn/"
        }
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-11-13T00:00:00.000Z",
          "value": "Advisory disclosed"
        },
        {
          "lang": "en",
          "time": "2026-11-13T01:00:00.000Z",
          "value": "VulDB entry created"
        },
        {
          "lang": "en",
          "time": "2026-11-13T21:02:27.000Z",
          "value": "VulDB entry last update"
        }
      ],
      "title": "Tenda AC18 Firmware Upgrade upgrade data authenticity",
      "x_generator": [
        "VulDB PVTS v202611"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
    "assignerShortName": "VulDB",
    "cveId": "CVE-2026-129258",
    "datePublished": "2026-11-14T14:30:22.937Z",
    "dateReserved": "2026-11-13T19:57:13.854Z",
    "dateUpdated": "2026-11-16T15:37:49.793Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-127204 (GCVE-0-2026-127204)

Vulnerability from cvelistv5 – Published: 2026-11-12 17:46 – Updated: 2026-11-13 18:59 X_Open Source
VLAI
Title
WooCommerce PayPal Pro Payment Gateway < 4.1.1 Payment Bypass via pp_capture_order
Summary
WooCommerce PayPal Pro Payment Gateway plugin before 4.1.1 contains an unauthenticated payment bypass vulnerability that allows remote attackers to mark unpaid orders as paid by exploiting the pp_capture_order AJAX handler, which is gated only by a public checkout nonce and fails to properly validate the PayPal capture response status. Attackers can supply a valid _paypal_order_id to trigger payment_complete() without verifying the capture status or amount, causing the store to fulfill goods or services that were never paid for and resulting in direct financial loss to the merchant.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 18:58 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Date Public
2026-11-10 00:00
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-127204",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T18:58:47.797078Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T18:59:29.502Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Payment Gateway for PayPal Pro, PayPal Checkout \u0026 Subscriptions for WooCommerce",
          "vendor": "wp.insider",
          "versions": [
            {
              "lessThan": "4.1.1",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "buiih"
        }
      ],
      "datePublic": "2026-11-10T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "WooCommerce PayPal Pro Payment Gateway plugin before 4.1.1 contains an unauthenticated payment bypass vulnerability that allows remote attackers to mark unpaid orders as paid by exploiting the pp_capture_order AJAX handler, which is gated only by a public checkout nonce and fails to properly validate the PayPal capture response status. Attackers can supply a valid _paypal_order_id to trigger payment_complete() without verifying the capture status or amount, causing the store to fulfill goods or services that were never paid for and resulting in direct financial loss to the merchant."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "HIGH",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-12T17:46:44.117Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "WordPress Changelog",
          "tags": [
            "release-notes",
            "patch"
          ],
          "url": "https://wordpress.org/plugins/woocommerce-paypal-pro-payment-gateway/#developers"
        },
        {
          "name": "VulnCheck Advisory: WooCommerce PayPal Pro Payment Gateway \u003c 4.1.1 Payment Bypass via pp_capture_order",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order"
        }
      ],
      "tags": [
        "x_open-source"
      ],
      "title": "WooCommerce PayPal Pro Payment Gateway \u003c 4.1.1 Payment Bypass via pp_capture_order",
      "x_generator": {
        "engine": "vulncheck"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-127204",
    "datePublished": "2026-11-12T17:46:44.117Z",
    "dateReserved": "2026-11-12T16:30:10.903Z",
    "dateUpdated": "2026-11-13T18:59:29.502Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126543 (GCVE-0-2026-126543)

Vulnerability from cvelistv5 – Published: 2026-11-11 00:58 – Updated: 2026-11-13 16:33
VLAI
Title
WWBN AVideo through 29.7.1 Wallet Credit Manipulation via PayPalYPT ipnV2.php
Summary
WWBN AVideo through 29.7.1 contains an improper payment verification vulnerability in plugin/PayPalYPT/ipnV2.php that credits wallets from PayPal IPNs not bound to the site's merchant account. Unauthenticated attackers can forward genuine VERIFIED recurring-payment IPNs from their own PayPal account with a chosen users_id to add wallet balance each billing cycle.
SSVC
Exploitation: poc Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 16:32 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
Impacted products
Vendor Product Version
WWBN AVideo Affected: 0 , ≤ 29.7.1 (semver)
    cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-09 17:59
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126543",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T16:32:32.923717Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T16:33:14.549Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-5gg3-9jhh-xf86"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:github/WWBN/AVideo",
          "product": "AVideo",
          "repo": "https://github.com/WWBN/AVideo",
          "vendor": "WWBN",
          "versions": [
            {
              "lessThanOrEqual": "29.7.1",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "29.7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "AlpetGexha"
        }
      ],
      "datePublic": "2026-11-09T17:59:26.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "WWBN AVideo through 29.7.1 contains an improper payment verification vulnerability in plugin/PayPalYPT/ipnV2.php that credits wallets from PayPal IPNs not bound to the site\u0027s merchant account. Unauthenticated attackers can forward genuine VERIFIED recurring-payment IPNs from their own PayPal account with a chosen users_id to add wallet balance each billing cycle."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "HIGH"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T00:58:54.710Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-5gg3-9jhh-xf86)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-5gg3-9jhh-xf86"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/WWBN/AVideo/commit/98406b7944e035e72082665ac886d78fc3af0a7f"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/WWBN/AVideo/blob/v29.7.1/plugin/PayPalYPT/ipnV2.php#L87-L125"
        },
        {
          "name": "VulnCheck Advisory: WWBN AVideo through 29.7.1 Wallet Credit Manipulation via PayPalYPT ipnV2.php",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/wwbn-avideo-through-29.7.1-wallet-credit-manipulation-via-paypalypt-ipnv2-php"
        }
      ],
      "title": "WWBN AVideo through 29.7.1 Wallet Credit Manipulation via PayPalYPT ipnV2.php",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126543",
    "datePublished": "2026-11-11T00:58:54.710Z",
    "dateReserved": "2026-11-11T00:33:10.272Z",
    "dateUpdated": "2026-11-13T16:33:14.549Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126084 (GCVE-0-2026-126084)

Vulnerability from cvelistv5 – Published: 2026-11-10 21:11 – Updated: 2026-11-12 19:10
VLAI
Title
Active Storage: Unsigned Content-Type in Active Storage GCS direct uploads with cache_control
Summary
Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application's bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application's, but could register a Service Worker scoped to the bucket path and read or replace a victim's later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-12 19:10 UTC
CWE
  • CWE-345 - Insufficient Verification of Data Authenticity
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 8155 records in the last 180 days details
Impacted products
Vendor Product Version
rails rails Affected: >= 8.1, < 8.1.4.1
Affected: < 8.0.5.2
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126084",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-12T19:10:19.483535Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-12T19:10:37.745Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "rails",
          "vendor": "rails",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 8.1, \u003c 8.1.4.1"
            },
            {
              "status": "affected",
              "version": "\u003c 8.0.5.2"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application\u0027s bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application\u0027s, but could register a Service Worker scoped to the bucket path and read or replace a victim\u0027s later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345: Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-10T21:11:00.234Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/rails/rails/security/advisories/GHSA-3w93-6hmw-whh4",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/rails/rails/security/advisories/GHSA-3w93-6hmw-whh4"
        },
        {
          "name": "https://github.com/rails/rails/commit/8d93f6a872e9550a91bf0e4fce50083a235ef3b1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/commit/8d93f6a872e9550a91bf0e4fce50083a235ef3b1"
        },
        {
          "name": "https://github.com/rails/rails/commit/ddc08ba61a8001e7402864c62e466cf732fc7614",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/commit/ddc08ba61a8001e7402864c62e466cf732fc7614"
        },
        {
          "name": "https://github.com/rails/rails/releases/tag/v8.0.5.2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/releases/tag/v8.0.5.2"
        },
        {
          "name": "https://github.com/rails/rails/releases/tag/v8.1.4.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/releases/tag/v8.1.4.1"
        }
      ],
      "source": {
        "advisory": "GHSA-3w93-6hmw-whh4",
        "discovery": "UNKNOWN"
      },
      "title": "Active Storage: Unsigned Content-Type in Active Storage GCS direct uploads with cache_control"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-126084",
    "datePublished": "2026-11-10T21:11:00.234Z",
    "dateReserved": "2026-11-10T17:07:43.285Z",
    "dateUpdated": "2026-11-12T19:10:37.745Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-123802 (GCVE-0-2026-123802)

Vulnerability from cvelistv5 – Published: 2026-11-09 18:23 – Updated: 2026-11-13 12:35
VLAI
Title
SuperTokens Core SAML: identity taken from an assertion that never passed the audience check, allowing sign-in as any IdP user
Summary
SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check. When the identity provider uses assertion-level signing, an attacker who has a still-valid IdP-signed assertion naming the victim for any audience and the attacker's own valid assertion for the target audience can combine them because validateSamlResponseAudience accepts an audience from one assertion while extractAllClaims takes the final NameID and attributes from another; response-level signing does not expose this multi-assertion variant. Independently, an assertion from an identity provider configured for the target deployment but issued to another SuperTokens deployment using the shared default saml_sp_entity_id can satisfy the target's audience check. Successful exploitation authenticates the attacker as the victim IdP user. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1.
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 12:34 UTC
CWE
  • CWE-287 - Improper Authentication
  • CWE-345 - Insufficient Verification of Data Authenticity
  • CWE-1220 - Insufficient Granularity of Access Control
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 8155 records in the last 180 days details
Impacted products
Vendor Product Version
supertokens supertokens-core Affected: >= 11.3.0, < 11.3.8
Affected: >= 11.4.0, < 11.4.8
Affected: >= 12.0.0, < 12.0.11
Affected: >= 12.1.0, < 12.1.2
Affected: >= 12.2.0, < 12.2.1
Affected: >= 12.3.0, < 12.3.1
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-123802",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T12:34:58.126841Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T12:35:15.061Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "supertokens-core",
          "vendor": "supertokens",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 11.3.0, \u003c 11.3.8"
            },
            {
              "status": "affected",
              "version": "\u003e= 11.4.0, \u003c 11.4.8"
            },
            {
              "status": "affected",
              "version": "\u003e= 12.0.0, \u003c 12.0.11"
            },
            {
              "status": "affected",
              "version": "\u003e= 12.1.0, \u003c 12.1.2"
            },
            {
              "status": "affected",
              "version": "\u003e= 12.2.0, \u003c 12.2.1"
            },
            {
              "status": "affected",
              "version": "\u003e= 12.3.0, \u003c 12.3.1"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check. When the identity provider uses assertion-level signing, an attacker who has a still-valid IdP-signed assertion naming the victim for any audience and the attacker\u0027s own valid assertion for the target audience can combine them because validateSamlResponseAudience accepts an audience from one assertion while extractAllClaims takes the final NameID and attributes from another; response-level signing does not expose this multi-assertion variant. Independently, an assertion from an identity provider configured for the target deployment but issued to another SuperTokens deployment using the shared default saml_sp_entity_id can satisfy the target\u0027s audience check. Successful exploitation authenticates the attacker as the victim IdP user. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 8.1,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287: Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-345",
              "description": "CWE-345: Insufficient Verification of Data Authenticity",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-1220",
              "description": "CWE-1220: Insufficient Granularity of Access Control",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-09T18:23:40.216Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/supertokens/supertokens-core/security/advisories/GHSA-wfg2-vqfg-rqh6",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/supertokens/supertokens-core/security/advisories/GHSA-wfg2-vqfg-rqh6"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b70125b4030ab6c",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b70125b4030ab6c"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7d8364f8df402f",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7d8364f8df402f"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be185f92f31e445",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be185f92f31e445"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74294d6c68d3859",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74294d6c68d3859"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe57851fa08d06a248",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe57851fa08d06a248"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2186381ad9cdd6",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2186381ad9cdd6"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83df9a150d6f3cf",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83df9a150d6f3cf"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f831cca8300081",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f831cca8300081"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7bbfc680de56dd",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7bbfc680de56dd"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf50ffbcdf332ee5",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf50ffbcdf332ee5"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21a960cb4ada083",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21a960cb4ada083"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v11.3.8",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v11.3.8"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v11.4.8",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v11.4.8"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v12.0.11",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v12.0.11"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v12.1.2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v12.1.2"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v12.2.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v12.2.1"
        },
        {
          "name": "https://github.com/supertokens/supertokens-core/releases/tag/v12.3.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/supertokens/supertokens-core/releases/tag/v12.3.1"
        }
      ],
      "source": {
        "advisory": "GHSA-wfg2-vqfg-rqh6",
        "discovery": "UNKNOWN"
      },
      "title": "SuperTokens Core SAML: identity taken from an assertion that never passed the audience check, allowing sign-in as any IdP user"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-123802",
    "datePublished": "2026-11-09T18:23:40.216Z",
    "dateReserved": "2026-11-06T15:27:56.226Z",
    "dateUpdated": "2026-11-13T12:35:15.061Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

No mitigation information available for this CWE.

CAPEC-111: JSON Hijacking (aka JavaScript Hijacking)

An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.

CAPEC-141: Cache Poisoning

An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.

CAPEC-142: DNS Cache Poisoning

A domain name server translates a domain name (such as www.example.com) into an IP address that Internet hosts use to contact Internet resources. An adversary modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the adversary specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Adversaries can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.

CAPEC-148: Content Spoofing

An adversary modifies content to make it contain something other than what the original content producer intended while keeping the apparent source of the content unchanged. The term content spoofing is most often used to describe modification of web pages hosted by a target to display the adversary's content instead of the owner's content. However, any content can be spoofed, including the content of email messages, file transfers, or the content of other network communication protocols. Content can be modified at the source (e.g. modifying the source file for a web page) or in transit (e.g. intercepting and modifying a message between the sender and recipient). Usually, the adversary will attempt to hide the fact that the content has been modified, but in some cases, such as with web site defacement, this is not necessary. Content Spoofing can lead to malware exposure, financial fraud (if the content governs financial transactions), privacy violations, and other unwanted outcomes.

CAPEC-218: Spoofing of UDDI/ebXML Messages

An attacker spoofs a UDDI, ebXML, or similar message in order to impersonate a service provider in an e-business transaction. UDDI, ebXML, and similar standards are used to identify businesses in e-business transactions. Among other things, they identify a particular participant, WSDL information for SOAP transactions, and supported communication protocols, including security protocols. By spoofing one of these messages an attacker could impersonate a legitimate business in a transaction or could manipulate the protocols used between a client and business. This could result in disclosure of sensitive information, loss of message integrity, or even financial fraud.

CAPEC-384: Application API Message Manipulation via Man-in-the-Middle

An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to perform adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system. Despite the use of AiTH software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Adversary-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.

CAPEC-385: Transaction or Event Tampering via Application API Manipulation

An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.

CAPEC-386: Application API Navigation Remapping

An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.

CAPEC-387: Navigation Remapping To Propagate Malicious Content

An adversary manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic.

CAPEC-388: Application API Button Hijacking

An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.

CAPEC-665: Exploitation of Thunderbolt Protection Flaws

An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

CAPEC-701: Browser in the Middle (BiTM)

An adversary exploits the inherent functionalities of a web browser, in order to establish an unnoticed remote desktop connection in the victim's browser to the adversary's system. The adversary must deploy a web client with a remote desktop session that the victim can access.