Common Weakness Enumeration

CWE-200

Weakness Discouraged

Exposure of Sensitive Information to an Unauthorized Actor

Abstraction: Class · Status: Draft

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Technical nuance

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

private, personal information, such as personal messages, financial data, health records, geographic location, or contact details

system status and environment, such as the operating system and installed packages

business secrets and intellectual property

network status and configuration

the product's own code or internal state

metadata, e.g. logging of connections or message headers

indirect information, such as a discrepancy between two internal operations that can be observed by an outsider

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

the product's own users

people or organizations whose information is created or used by the product, even if they are not direct product users

the product's administrators, including the admins of the system(s) and/or networks on which the product operates

the developer

Information exposures can occur in different ways:

the code explicitly inserts sensitive information into resources or messages that are intentionally made accessible to unauthorized actors, but should not contain the information - i.e., the information should have been "scrubbed" or "sanitized"

a different weakness or mistake indirectly inserts the sensitive information into resources, such as a web script error revealing the full system path of the program.

the code manages resources that intentionally contain sensitive information, but the resources are unintentionally made accessible to unauthorized actors. In this case, the information exposure is resultant - i.e., a different weakness enabled the access to the information in the first place.

Mapping guidance

CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information. Unfortunately, CWE-200 is commonly misused to represent the loss of confidentiality in a vulnerability. From the CWE perspective, loss of confidentiality is a technical impact, not a root cause error. Loss of confidentiality can arize from many different weaknesses, such as insecure file permissions or out-of-bounds read. As of CWE 4.20, over 400 CWE entries can lead to a loss of confidentiality. Other options are often available. [REF-1287].

If an error or mistake causes information to be disclosed, then use the CWE ID for that error.

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

Automated Static Analysis - Binary or Bytecode

According to SOAR [REF-1479], the following detection techniques may be useful:

Cost effective for partial coverage:

Bytecode Weakness Analysis - including disassembler + source code weakness analysis

Inter-application Flow Analysis

Effectiveness: SOAR Partial

Dynamic Analysis with Automated Results Interpretation

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Web Application Scanner

Web Services Scanner

Database Scanners

Effectiveness: High

Dynamic Analysis with Manual Results Interpretation

According to SOAR [REF-1479], the following detection techniques may be useful:

Cost effective for partial coverage:

Fuzz Tester

Framework-based Fuzzer

Automated Monitored Execution

Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious

Effectiveness: SOAR Partial

Manual Static Analysis - Source Code

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Manual Source Code Review (not inspections)

Effectiveness: High

Automated Static Analysis - Source Code

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Context-configured Source Code Weakness Analyzer

Cost effective for partial coverage:

Source code Weakness Analyzer

Effectiveness: High

Architecture or Design Review

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Formal Methods / Correct-By-Construction

Cost effective for partial coverage:

Attack Modeling

Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

Effectiveness: High

Content history
Submission: PLOVER · 2006-07-19 · CWE Draft 3
Contribution: Nick Johnston · 2022-07-11 · CWE 4.9

Identified incorrect language tag in demonstrative example.

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 Likelihood_of_Exploit, Relationships, Taxonomy_Mappings, Weakness_Ordinalities

Modification: CWE Content Team · MITRE · 2008-10-14 · CWE 1.0.1

updated Description

Modification: CWE Content Team · MITRE · 2009-12-28 · CWE 1.7

updated Alternate_Terms, Description, Name

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 · 2011-03-29 · CWE 1.12

updated Description, Relationships

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

updated Common_Consequences

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

updated Related_Attack_Patterns, Relationships

Modification: CWE Content Team · MITRE · 2012-10-30 · CWE 2.3

updated Potential_Mitigations

Modification: CWE Content Team · MITRE · 2013-02-21 · CWE 2.4

updated Alternate_Terms, Applicable_Platforms, References

Modification: CWE Content Team · MITRE · 2014-06-23 · CWE 2.7

updated Related_Attack_Patterns

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

updated Detection_Factors, 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 References

Modification: CWE Content Team · MITRE · 2019-01-03 · CWE 3.2

updated Related_Attack_Patterns

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

updated Related_Attack_Patterns, Relationships

Modification: CWE Content Team · MITRE · 2019-09-19 · CWE 3.4

updated Demonstrative_Examples, Observed_Examples, Relationships

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

updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Observed_Examples, Related_Attack_Patterns, Relationships, Weakness_Ordinalities

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 Alternate_Terms, Description, Maintenance_Notes, Related_Attack_Patterns, Relationships

Modification: CWE Content Team · MITRE · 2020-12-10 · CWE 4.3

updated Potential_Mitigations

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

updated Relationships

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

updated Relationships

Modification: CWE Content Team · MITRE · 2022-10-13 · CWE 4.9

updated Demonstrative_Examples, Maintenance_Notes, Observed_Examples, References

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

updated References, Relationships

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

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2023-10-26 · CWE 4.13

updated Observed_Examples

Modification: CWE Content Team · MITRE · 2024-11-19 · CWE 4.16

updated Relationships

Modification: CWE Content Team · MITRE · 2025-04-03 · CWE 4.17

updated Relationships

Modification: CWE Content Team · MITRE · 2025-09-09 · CWE 4.18

updated Detection_Factors, References

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

updated Applicable_Platforms, Relationships

Modification: CWE Content Team · MITRE · 2026-04-30 · CWE 4.20

updated Maintenance_Notes, Mapping_Notes

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

updated Alternate_Terms, Description, Mapping_Notes, Relationships, Technical_Nuance

16797 vulnerabilities reference this CWE, most recent first.

CVE-2026-134364 (GCVE-0-2026-134364)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
pypdf 3.7.1 before 7.0.0 Placeholder Recovery via File Identifier in Encrypted Documents
Summary
pypdf 3.7.1 before 7.0.0 contains an information disclosure vulnerability that allows attackers to guess placeholders in encrypted templated documents by analyzing file identifiers. Attackers with a document sharing the same template and access to other documents' file identifiers can recover placeholder contents from encrypted PDFs.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
py-pdf pypdf Affected: 3.7.1 , < 7.0.0 (semver)
Unaffected: 7.0.0 (semver)
    cpe:2.3:a:py-pdf:pypdf:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-06 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:pypi/pypdf",
          "product": "pypdf",
          "vendor": "py-pdf",
          "versions": [
            {
              "lessThan": "7.0.0",
              "status": "affected",
              "version": "3.7.1",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "7.0.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:py-pdf:pypdf:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.0",
                  "versionStartIncluding": "3.7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "superboy-zjc"
        }
      ],
      "datePublic": "2026-11-06T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "pypdf 3.7.1 before 7.0.0 contains an information disclosure vulnerability that allows attackers to guess placeholders in encrypted templated documents by analyzing file identifiers. Attackers with a document sharing the same template and access to other documents\u0027 file identifiers can recover placeholder contents from encrypted PDFs."
        }
      ],
      "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:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:16.784Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-mwj3-fpmc-hjcv)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv"
        },
        {
          "name": "VulnCheck Advisory: pypdf 3.7.1 before 7.0.0 Placeholder Recovery via File Identifier in Encrypted Documents",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents"
        }
      ],
      "title": "pypdf 3.7.1 before 7.0.0 Placeholder Recovery via File Identifier in Encrypted Documents",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134364",
    "datePublished": "2026-11-21T16:34:16.784Z",
    "dateReserved": "2026-11-21T00:01:23.102Z",
    "dateUpdated": "2026-11-21T16:34:16.784Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134355 (GCVE-0-2026-134355)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
AzuraCast before 0.24.1 Icecast Password Exposure via profile/edit Endpoint
Summary
AzuraCast before 0.24.1 contains an improper authorization vulnerability in the /api/station/{station_id}/profile/edit endpoint that exposes and accepts Icecast/Shoutcast passwords for users holding Manage Station Profile without Manage Station Broadcasting. Authenticated station users can read the admin, source, relay and streamer passwords via GET to administer Icecast or broadcast to listeners, or overwrite them via PUT to lock out operators.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
AzuraCast AzuraCast Affected: 0 , < 0.24.1 (semver)
Unaffected: 0.24.1 (semver)
    cpe:2.3:a:azuracast:azuracast:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-05 00:00
Credits
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "AzuraCast",
          "vendor": "AzuraCast",
          "versions": [
            {
              "lessThan": "0.24.1",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "0.24.1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:azuracast:azuracast:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "0.24.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "kats1123"
        }
      ],
      "datePublic": "2026-11-05T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "AzuraCast before 0.24.1 contains an improper authorization vulnerability in the /api/station/{station_id}/profile/edit endpoint that exposes and accepts Icecast/Shoutcast passwords for users holding Manage Station Profile without Manage Station Broadcasting. Authenticated station users can read the admin, source, relay and streamer passwords via GET to administer Icecast or broadcast to listeners, or overwrite them via PUT to lock out operators."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.4,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:24.451Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-r23w-hv44-7pjq)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-r23w-hv44-7pjq"
        },
        {
          "name": "VulnCheck Advisory: AzuraCast before 0.24.1 Icecast Password Exposure via profile/edit Endpoint",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/azuracast-before-0.24.1-icecast-password-exposure-via-profile-edit-endpoint"
        }
      ],
      "title": "AzuraCast before 0.24.1 Icecast Password Exposure via profile/edit Endpoint",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134355",
    "datePublished": "2026-11-21T16:34:24.451Z",
    "dateReserved": "2026-11-21T00:00:14.019Z",
    "dateUpdated": "2026-11-21T16:34:24.451Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134353 (GCVE-0-2026-134353)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
rclone before 1.76.0 Credential Leak via Swift, NetStorage and Seafile Redirects
Summary
rclone before 1.76.0 leaks credentials in its swift, netstorage and seafile backends, which follow HTTP redirects using Go's default policy: swift and netstorage send auth headers or passwords on cross-host or HTTPS-to-HTTP redirects, and seafile sends API tokens or passwords on same-host HTTPS-to-HTTP redirects. Attackers receiving or observing a redirect issued by the configured endpoint can capture these credentials to access storage or replay signed requests.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
rclone rclone Affected: 0 , < 1.76.0 (semver)
Unaffected: 1.76.0 (semver)
    cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-06 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:golang/github.com/rclone/rclone",
          "product": "rclone",
          "vendor": "rclone",
          "versions": [
            {
              "lessThan": "1.76.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.76.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.76.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "ncw"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "manus-use"
        }
      ],
      "datePublic": "2026-11-06T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "rclone before 1.76.0 leaks credentials in its swift, netstorage and seafile backends, which follow HTTP redirects using Go\u0027s default policy: swift and netstorage send auth headers or passwords on cross-host or HTTPS-to-HTTP redirects, and seafile sends API tokens or passwords on same-host HTTPS-to-HTTP redirects. Attackers receiving or observing a redirect issued by the configured endpoint can capture these credentials to access storage or replay signed requests."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:27.189Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-m97j-7x65-wh93)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/rclone/rclone/security/advisories/GHSA-m97j-7x65-wh93"
        },
        {
          "name": "VulnCheck Advisory: rclone before 1.76.0 Credential Leak via Swift, NetStorage and Seafile Redirects",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/rclone-before-1.76.0-credential-leak-via-swift-netstorage-and-seafile-redirects"
        }
      ],
      "title": "rclone before 1.76.0 Credential Leak via Swift, NetStorage and Seafile Redirects",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134353",
    "datePublished": "2026-11-21T16:34:27.189Z",
    "dateReserved": "2026-11-21T00:00:14.019Z",
    "dateUpdated": "2026-11-21T16:34:27.189Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134334 (GCVE-0-2026-134334)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
ArcadeDB 26.7.1 before 26.11.1 Information Disclosure via Full-Text BM25 Statistics
Summary
ArcadeDB from 26.7.1 before 26.11.1 contains an information disclosure vulnerability because LSMTreeFullTextIndex computes BM25 corpus statistics over all buckets of the indexed type, ignoring bucket access control on subtypes. Authenticated users with read access to a supertype but not its subtype can run EXPLAIN or PROFILE on full-text queries and read totalDocs and per-term df values to count hidden subtype documents containing chosen terms.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
ArcadeData arcadedb Affected: 26.7.1 , < 26.11.1 (semver)
Unaffected: 26.11.1 (semver)
Create a notification for this product.
Date Public
2026-11-04 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:maven/com.arcadedb/arcadedb-engine",
          "product": "arcadedb",
          "vendor": "ArcadeData",
          "versions": [
            {
              "lessThan": "26.11.1",
              "status": "affected",
              "version": "26.7.1",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "26.11.1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "datePublic": "2026-11-04T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "ArcadeDB from 26.7.1 before 26.11.1 contains an information disclosure vulnerability because LSMTreeFullTextIndex computes BM25 corpus statistics over all buckets of the indexed type, ignoring bucket access control on subtypes. Authenticated users with read access to a supertype but not its subtype can run EXPLAIN or PROFILE on full-text queries and read totalDocs and per-term df values to count hidden subtype documents containing chosen terms."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "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:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:41.768Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-875c-3v5j-4wh2)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-875c-3v5j-4wh2"
        },
        {
          "name": "VulnCheck Advisory: ArcadeDB 26.7.1 before 26.11.1 Information Disclosure via Full-Text BM25 Statistics",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/arcadedb-26.7.1-before-26.11.1-information-disclosure-via-full-text-bm25-statistics"
        }
      ],
      "title": "ArcadeDB 26.7.1 before 26.11.1 Information Disclosure via Full-Text BM25 Statistics",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134334",
    "datePublished": "2026-11-21T16:34:41.768Z",
    "dateReserved": "2026-11-20T23:57:19.685Z",
    "dateUpdated": "2026-11-21T16:34:41.768Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134281 (GCVE-0-2026-134281)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:35 – Updated: 2026-11-21 16:35
VLAI
Title
Vikunja 2.2.0 before 2.8.0 Information Disclosure via tasks.overdue Webhook Payload
Summary
Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to read other users' private projects through the tasks.overdue webhook payload. Attackers can register a personal tasks.overdue webhook with one subscribed overdue task, then receive project titles, descriptions, and owner IDs from other users' reminders at external URLs.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
go-vikunja vikunja Affected: 2.2.0 , < 2.8.0 (semver)
Unaffected: 2.8.0 (semver)
    cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-05 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:golang/code.vikunja.io/api",
          "product": "vikunja",
          "vendor": "go-vikunja",
          "versions": [
            {
              "lessThan": "2.8.0",
              "status": "affected",
              "version": "2.2.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "2.8.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2.8.0",
                  "versionStartIncluding": "2.2.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "datePublic": "2026-11-05T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to read other users\u0027 private projects through the tasks.overdue webhook payload. Attackers can register a personal tasks.overdue webhook with one subscribed overdue task, then receive project titles, descriptions, and owner IDs from other users\u0027 reminders at external URLs."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:35:23.356Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-pp3p-qw5m-rgm2)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pp3p-qw5m-rgm2"
        },
        {
          "name": "VulnCheck Advisory: Vikunja 2.2.0 before 2.8.0 Information Disclosure via tasks.overdue Webhook Payload",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/vikunja-2.2.0-before-2.8.0-information-disclosure-via-tasks-overdue-webhook-payload"
        }
      ],
      "title": "Vikunja 2.2.0 before 2.8.0 Information Disclosure via tasks.overdue Webhook Payload",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134281",
    "datePublished": "2026-11-21T16:35:23.356Z",
    "dateReserved": "2026-11-20T23:47:55.597Z",
    "dateUpdated": "2026-11-21T16:35:23.356Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134272 (GCVE-0-2026-134272)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:35 – Updated: 2026-11-21 16:35
VLAI
Title
Vikunja 0.9.0 before 2.8.0 Email Disclosure via Project Link Share List
Summary
Vikunja from 0.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators' email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
go-vikunja vikunja Affected: 0.9.0 , < 2.8.0 (semver)
Unaffected: 2.8.0 (semver)
    cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-05 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:golang/code.vikunja.io/api",
          "product": "vikunja",
          "vendor": "go-vikunja",
          "versions": [
            {
              "lessThan": "2.8.0",
              "status": "affected",
              "version": "0.9.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "2.8.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2.8.0",
                  "versionStartIncluding": "0.9.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "datePublic": "2026-11-05T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Vikunja from 0.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators\u0027 email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.1,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "HIGH",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 2.7,
            "baseSeverity": "LOW",
            "confidentialityImpact": "LOW",
            "integrityImpact": "NONE",
            "privilegesRequired": "HIGH",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:35:33.990Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-8g2q-76h7-8fh7)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7"
        },
        {
          "name": "VulnCheck Advisory: Vikunja 0.9.0 before 2.8.0 Email Disclosure via Project Link Share List",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/vikunja-0.9.0-before-2.8.0-email-disclosure-via-project-link-share-list"
        }
      ],
      "title": "Vikunja 0.9.0 before 2.8.0 Email Disclosure via Project Link Share List",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134272",
    "datePublished": "2026-11-21T16:35:33.990Z",
    "dateReserved": "2026-11-20T23:47:04.849Z",
    "dateUpdated": "2026-11-21T16:35:33.990Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134248 (GCVE-0-2026-134248)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:35 – Updated: 2026-11-21 16:35
VLAI
Title
SiYuan 3.6.0 before 3.8.10 Information Disclosure via copyStdMarkdown Block References
Summary
SiYuan 3.6.0 before 3.8.10 contains an information disclosure vulnerability that allows authenticated Readers to read protected documents through block-reference footnote resolution in Markdown export. Attackers can request copyStdMarkdown for a public document referencing a hidden, disabled, or password-protected document to disclose its body text without the publish password.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
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
siyuan-note siyuan Affected: 3.6.0 , < 3.8.10 (semver)
Unaffected: 3.8.10 (semver)
Create a notification for this product.
Date Public
2026-11-05 00:00
Credits
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/siyuan-note/siyuan",
          "product": "siyuan",
          "vendor": "siyuan-note",
          "versions": [
            {
              "lessThan": "3.8.10",
              "status": "affected",
              "version": "3.6.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "3.8.10",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "garnetarc"
        }
      ],
      "datePublic": "2026-11-05T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "SiYuan 3.6.0 before 3.8.10 contains an information disclosure vulnerability that allows authenticated Readers to read protected documents through block-reference footnote resolution in Markdown export. Attackers can request copyStdMarkdown for a public document referencing a hidden, disabled, or password-protected document to disclose its body text without the publish password."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.3,
            "baseSeverity": "HIGH",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "HIGH",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.7,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:35:58.057Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-qwg4-fj37-jjqq)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qwg4-fj37-jjqq"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/siyuan-note/siyuan/commit/7b70b90a5ec49b13f81b5f2779f57a7fdf53dd57"
        },
        {
          "name": "VulnCheck Advisory: SiYuan 3.6.0 before 3.8.10 Information Disclosure via copyStdMarkdown Block References",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/siyuan-3.6.0-before-3.8.10-information-disclosure-via-copystdmarkdown-block-references"
        }
      ],
      "title": "SiYuan 3.6.0 before 3.8.10 Information Disclosure via copyStdMarkdown Block References",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134248",
    "datePublished": "2026-11-21T16:35:58.057Z",
    "dateReserved": "2026-11-20T23:44:41.011Z",
    "dateUpdated": "2026-11-21T16:35:58.057Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134244 (GCVE-0-2026-134244)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:36 – Updated: 2026-11-21 16:36
VLAI
Title
SiYuan 3.8.0 before 3.8.10 LAN Sync Metadata Disclosure Before Peer Authentication
Summary
SiYuan 3.8.0 before 3.8.10 contains an information disclosure vulnerability in LAN sync that allows adjacent unauthenticated attackers to obtain device metadata by advertising a counterfeit peer with a replayed discovery tag. The client sends the sync scope ID, device name, OS, app version, and TLS client certificate to /peer-sync/v1/session/open before validating the server proof.
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
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
siyuan-note siyuan Affected: 3.8.0 , < 3.8.10 (semver)
Unaffected: 3.8.10 (semver)
    cpe:2.3:a:b3log:siyuan:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-06 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/SiYuan",
          "product": "siyuan",
          "vendor": "siyuan-note",
          "versions": [
            {
              "lessThan": "3.8.10",
              "status": "affected",
              "version": "3.8.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "3.8.10",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:b3log:siyuan:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "3.8.10",
                  "versionStartIncluding": "3.8.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "groveatlas300"
        }
      ],
      "datePublic": "2026-11-06T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "SiYuan 3.8.0 before 3.8.10 contains an information disclosure vulnerability in LAN sync that allows adjacent unauthenticated attackers to obtain device metadata by advertising a counterfeit peer with a replayed discovery tag. The client sends the sync scope ID, device name, OS, app version, and TLS client certificate to /peer-sync/v1/session/open before validating the server proof."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "ADJACENT",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:36:02.523Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-x5cg-xgq2-x369)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/siyuan-note/siyuan/commit/d89aaf4ecb6b1d203145a72714265164e3eace97"
        },
        {
          "name": "VulnCheck Advisory: SiYuan 3.8.0 before 3.8.10 LAN Sync Metadata Disclosure Before Peer Authentication",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication"
        }
      ],
      "title": "SiYuan 3.8.0 before 3.8.10 LAN Sync Metadata Disclosure Before Peer Authentication",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134244",
    "datePublished": "2026-11-21T16:36:02.523Z",
    "dateReserved": "2026-11-20T23:44:41.011Z",
    "dateUpdated": "2026-11-21T16:36:02.523Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-133855 (GCVE-0-2026-133855)

Vulnerability from cvelistv5 – Published: 2026-11-20 14:44 – Updated: 2026-11-20 16:32
VLAI
Title
flowintel: Unauthorized Disclosure of Linked Case References in Case History
Summary
flowintel contains an information disclosure vulnerability in its case history feature. When a user views the history of a case they are authorized to access, the history output includes references to other cases (linked, unlinked, or forked) without verifying whether the requesting user has permission to view those referenced cases. This exposes the identifiers and titles of cases that the user should not be able to discover. The vulnerability affects multiple output paths: - Browser-based case history view - API history endpoint - Plain-text history download - Markdown history download - Report timeline generation An authenticated user with access to any single case can enumerate the existence and identifiers of other cases by reading the history of a case they can access. This bypasses the intended per-case access control model and may reveal the existence of sensitive investigations, their identifiers, and associated metadata to unauthorized users. The raw audit storage is not modified; the issue is solely in the presentation layer failing to filter references to inaccessible cases before returning history data to the user. Affected versions: flowintel prior to 4.1.0.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-20 14:43 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 16:22 UTC
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-862 - Missing Authorization
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
flowintel flowintel Affected: 0 , < 4.1.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
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-20 14:43
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809 407e73d34f15…
Confidence
medium
Commit Subject Patch SHA-256
c44025ea6810 fix: [security] Filter linked case references from case 407e73d34f15…
Fix summary

A new visibility-aware history retrieval function was introduced that parses each history record for case references (link, unlink, fork events) and checks the requesting user's access to every referenced case before including that record in the output. Records referencing inaccessible cases are omitted from the response. The filtering is applied consistently across all history output paths (browser view, API, text download, Markdown download, and report timelines). Administrative users retain full unfiltered access. The raw audit log storage remains unchanged to preserve forensic integrity.

Patch summary

Added a new function get_visible_history() in common_core.py that: (1) verifies the user can view the current case, (2) groups raw history lines into logical records using timestamp-based event boundaries, (3) extracts referenced case IDs from link/unlink/fork messages using regex patterns, (4) checks can_view_case() for each referenced case, and (5) excludes records referencing inaccessible cases. Updated download_history(), download_history_md(), the browser history endpoint, the API history endpoint, and the report timeline generator to call get_visible_history() instead of the raw get_history(). Added helper functions _history_case_references() and _history_record_complete() to handle legacy multiline link records and ambiguous formats. Changed download_history() to serve content via BytesIO instead of reading a file path directly.

CVSS rationale

AV:N - The vulnerability is exploitable over the network via the web application. AC:L - Exploitation requires only viewing the history of any accessible case; no special conditions or race conditions are needed. AT:N - No prior attack or manipulation of the target is required. PR:L - The attacker must be an authenticated user with access to at least one case. UI:N - No user interaction beyond normal application use is required. VC:L - The vulnerable component (case history endpoint) leaks limited information (case IDs and titles of referenced cases). VI:N - No integrity impact. VA:N - No availability impact. SC:L - Subsequent components (other cases) have their existence and identifiers exposed to unauthorized users. SI:N - No integrity impact on other systems. SA:N - No safety impact.

Weakness rationale
  • CWE-200 The case history output exposes identifiers and titles of other cases to users who do not have authorization to view those cases. The sensitive data (case existence, IDs, titles) is disclosed through a legitimate endpoint without proper per-reference authorization checks.
  • CWE-862 The history retrieval functions did not perform authorization checks on the referenced cases embedded within the history records. The primary case access was verified, but the secondary cases referenced in link/unlink/fork events were not checked before inclusion in the response.
Attack pattern rationale
  • CAPEC-128 The attacker leverages a legitimate application endpoint (case history) to discover metadata about other resources (case identifiers, titles, and relationships) that they are not authorized to access. This is the closest CAPEC pattern to the observed information disclosure through a functional endpoint. The mapping is approximate because CAPEC-128 typically refers to version/configuration discovery, whereas here the disclosed metadata is application data (case references) rather than system metadata. No more specific CAPEC pattern for cross-object information disclosure via a legitimate read endpoint exists in the CAPEC catalog.
Assumptions to verify
  • The affected version range is assumed to be all versions prior to 4.1.0 based on the explicit context providing affected_version '0' and fixed_version '4.1.0'. The exact earliest affected version is not confirmed by the patch itself.
  • The CAPEC-128 mapping is the closest available pattern; no CAPEC specifically covers cross-object information disclosure through a legitimate read endpoint. The mapping is approximate.
  • CVSS PR:L assumes the attacker needs at least one valid authenticated session with access to any case. If the application allows unauthenticated history access in some deployment, PR would be N.
  • The patch commit message references 'Tool: Codex' which is noted as the AI tool used for implementation but is not credited as a vulnerability finder or reporter.
  • The vulnerability requires the attacker to already have access to at least one case; it does not allow access to cases with no prior relationship to the attacker's accessible cases beyond those referenced in history.
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 7 11 medium 5
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-17 12:50 UTC Fix developed Corrective change authored (c44025ea68109996e3b1a0f01f6333caba190809): fix: [security] Filter linked case references from case https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809
  2. 2026-11-20 14:42 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133855",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:22:35.285570Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T16:32:51.484Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/case/CaseCore.py",
            "app/case/case.py",
            "app/case/case_api.py",
            "app/case/case_notes.py",
            "app/case/common_core.py"
          ],
          "product": "flowintel",
          "programFiles": [],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThan": "4.1.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "flowintel contains an information disclosure vulnerability in its case history feature. When a user views the history of a case they are authorized to access, the history output includes references to other cases (linked, unlinked, or forked) without verifying whether the requesting user has permission to view those referenced cases. This exposes the identifiers and titles of cases that the user should not be able to discover.\n\nThe vulnerability affects multiple output paths:\n- Browser-based case history view\n- API history endpoint\n- Plain-text history download\n- Markdown history download\n- Report timeline generation\n\nAn authenticated user with access to any single case can enumerate the existence and identifiers of other cases by reading the history of a case they can access. This bypasses the intended per-case access control model and may reveal the existence of sensitive investigations, their identifiers, and associated metadata to unauthorized users.\n\nThe raw audit storage is not modified; the issue is solely in the presentation layer failing to filter references to inaccessible cases before returning history data to the user.\n\nAffected versions: flowintel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-128",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-128 Application Metadata Discovery"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "LOW",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE",
            "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-20T14:43:12Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862 Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T14:44:59.907Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "A new visibility-aware history retrieval function was introduced that parses each history record for case references (link, unlink, fork events) and checks the requesting user\u0027s access to every referenced case before including that record in the output. Records referencing inaccessible cases are omitted from the response. The filtering is applied consistently across all history output paths (browser view, API, text download, Markdown download, and report timelines). Administrative users retain full unfiltered access. The raw audit log storage remains unchanged to preserve forensic integrity."
        }
      ],
      "title": "flowintel: Unauthorized Disclosure of Linked Case References in Case History",
      "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 version range is assumed to be all versions prior to 4.1.0 based on the explicit context providing affected_version \u00270\u0027 and fixed_version \u00274.1.0\u0027. The exact earliest affected version is not confirmed by the patch itself.",
                  "The CAPEC-128 mapping is the closest available pattern; no CAPEC specifically covers cross-object information disclosure through a legitimate read endpoint. The mapping is approximate.",
                  "CVSS PR:L assumes the attacker needs at least one valid authenticated session with access to any case. If the application allows unauthenticated history access in some deployment, PR would be N.",
                  "The patch commit message references \u0027Tool: Codex\u0027 which is noted as the AI tool used for implementation but is not credited as a vulnerability finder or reporter.",
                  "The vulnerability requires the attacker to already have access to at least one case; it does not allow access to cases with no prior relationship to the attacker\u0027s accessible cases beyond those referenced in history."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-128",
                    "rationale": "The attacker leverages a legitimate application endpoint (case history) to discover metadata about other resources (case identifiers, titles, and relationships) that they are not authorized to access. This is the closest CAPEC pattern to the observed information disclosure through a functional endpoint. The mapping is approximate because CAPEC-128 typically refers to version/configuration discovery, whereas here the disclosed metadata is application data (case references) rather than system metadata. No more specific CAPEC pattern for cross-object information disclosure via a legitimate read endpoint exists in the CAPEC catalog."
                  }
                ],
                "commit": "c44025ea68109996e3b1a0f01f6333caba190809",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N - The vulnerability is exploitable over the network via the web application. AC:L - Exploitation requires only viewing the history of any accessible case; no special conditions or race conditions are needed. AT:N - No prior attack or manipulation of the target is required. PR:L - The attacker must be an authenticated user with access to at least one case. UI:N - No user interaction beyond normal application use is required. VC:L - The vulnerable component (case history endpoint) leaks limited information (case IDs and titles of referenced cases). VI:N - No integrity impact. VA:N - No availability impact. SC:L - Subsequent components (other cases) have their existence and identifiers exposed to unauthorized users. SI:N - No integrity impact on other systems. SA:N - No safety impact.",
                "fixSummary": "A new visibility-aware history retrieval function was introduced that parses each history record for case references (link, unlink, fork events) and checks the requesting user\u0027s access to every referenced case before including that record in the output. Records referencing inaccessible cases are omitted from the response. The filtering is applied consistently across all history output paths (browser view, API, text download, Markdown download, and report timelines). Administrative users retain full unfiltered access. The raw audit log storage remains unchanged to preserve forensic integrity.",
                "generatedAt": "2026-11-20T14:43:12.693948Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 5,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 7
                    }
                  ],
                  "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": "407e73d34f154f6febfa70e71f7a7c5816cae0d73d6b25d0e6f4a411304336cd",
                "patchSummary": "Added a new function get_visible_history() in common_core.py that: (1) verifies the user can view the current case, (2) groups raw history lines into logical records using timestamp-based event boundaries, (3) extracts referenced case IDs from link/unlink/fork messages using regex patterns, (4) checks can_view_case() for each referenced case, and (5) excludes records referencing inaccessible cases. Updated download_history(), download_history_md(), the browser history endpoint, the API history endpoint, and the report timeline generator to call get_visible_history() instead of the raw get_history(). Added helper functions _history_case_references() and _history_record_complete() to handle legacy multiline link records and ambiguous formats. Changed download_history() to serve content via BytesIO instead of reading a file path directly.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "c44025ea68109996e3b1a0f01f6333caba190809",
                    "date": "Tue, 17 Nov 2026 13:50:29 +0100",
                    "patchSha256": "407e73d34f154f6febfa70e71f7a7c5816cae0d73d6b25d0e6f4a411304336cd",
                    "retrievedAt": "2026-11-20T14:42:40.710956Z",
                    "source": "https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809",
                    "subject": "fix: [security] Filter linked case references from case"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T14:43:12Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Filter linked case references from case",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-200",
                    "rationale": "The case history output exposes identifiers and titles of other cases to users who do not have authorization to view those cases. The sensitive data (case existence, IDs, titles) is disclosed through a legitimate endpoint without proper per-reference authorization checks."
                  },
                  {
                    "cweId": "CWE-862",
                    "rationale": "The history retrieval functions did not perform authorization checks on the referenced cases embedded within the history records. The primary case access was verified, but the secondary cases referenced in link/unlink/fork events were not checked before inclusion in the response."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (c44025ea68109996e3b1a0f01f6333caba190809): fix: [security] Filter linked case references from case",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809"
                    ],
                    "timestamp": "2026-11-17T12:50:29Z",
                    "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/flowintel/flowintel/commit/c44025ea68109996e3b1a0f01f6333caba190809"
                    ],
                    "timestamp": "2026-11-20T14:42:40.710956Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20423"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133855",
    "datePublished": "2026-11-20T14:44:59.907Z",
    "dateReserved": "2026-11-20T14:44:53.894Z",
    "dateUpdated": "2026-11-20T16:32:51.484Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-133853 (GCVE-0-2026-133853)

Vulnerability from cvelistv5 – Published: 2026-11-20 14:44 – Updated: 2026-11-20 16:33
VLAI
Title
FlowIntel Chatbot Shared MCP Session Allows Cross-User API Identity Confusion
Summary
FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request. Preconditions: - An authenticated user with access to the chatbot interface. - Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment. Impact: - A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases). - A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential. - The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface. Affected versions: FlowIntel prior to 4.1.0.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-20 14:41 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 16:21 UTC
CWE
  • CWE-290 - Authentication Bypass by Spoofing
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
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
flowintel flowintel Affected: 0 , < 4.1.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
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-20 14:41
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8 b2eb7327abee…
Confidence
medium
Commit Subject Patch SHA-256
9eec395cc73c fix: [security] Isolate chatbot MCP API identities b2eb7327abee…
Fix summary

The shared persistent MCP session and process-wide API key mutation were removed. Each chatbot tool invocation now spawns its own short-lived MCP child process with credentials resolved fresh from the authenticated request context. If the user's identity or API key is unavailable, the invocation is rejected before any child process is launched, preventing fallback to ambient or stale credentials. Each transport is deterministically closed on success, failure, or timeout, eliminating residual credential exposure.

Patch summary

Removed the global _mcp_session, _mcp_loop, _mcp_thread, _mcp_current_api_key state and the _ensure_mcp() / _start_mcp_background() / _run_mcp_session() functions that maintained a single shared asyncio event loop and thread. Replaced with _mcp_environment() which resolves the user's API key from the authenticated session on every call and raises RuntimeError if unavailable, and _call_mcp_tool() which opens a per-invocation stdio transport, executes the tool, and closes the transport in all exit paths. Eliminated all os.environ mutations of FLOWINTEL_API_KEY. Added 33 regression tests in tests/chatbot/test_api_identity.py covering concurrent identity isolation, ambient-credential rejection, detached-user handling, key rotation, transport cleanup on failure/timeout, and real stdio child-process lifecycle.

CVSS rationale

AV:N: the chatbot is a network-accessible Flask endpoint. AC:H: exploitation requires concurrent or carefully timed requests from two different users to trigger the shared-session race, or a specific sequence of credential writes to the process environment. AT:N: no manipulation of a separate target is needed. PR:L: the attacker must be an authenticated user with chatbot access. UI:N: no victim interaction beyond their own request is required. VC:H: a user can read another user's sensitive data (private cases, investigations). VI:N, VA:N: no integrity or availability impact is evidenced. SC:N, SI:N, SA:N: no impact on separate components is demonstrated.

Weakness rationale
  • CWE-290 The shared MCP session and process-wide environment variable allowed one user's authenticated identity (API key) to be applied to another user's tool invocation. The per-request identity was not isolated, effectively allowing identity confusion or spoofing between concurrent sessions.
  • CWE-200 Because credentials were shared across requests and written to the process environment, a user could access data (e.g., private cases) belonging to another user whose key was cached in the shared session or ambient environment.
Attack pattern rationale
  • CAPEC-126 The closest available CAPEC. The shared MCP session acted as a single long-lived session whose credentials could be 'hijacked' by a concurrent request from a different user, causing the wrong identity to be used. No CAPEC specifically covers 'shared per-tenant credential state in a multi-user service,' so CAPEC-126 is the best approximation. Uncertainty: the attack does not involve a traditional network-level session token theft but rather a server-side shared-state race.
Assumptions to verify
  • AC:H is assumed because reliable exploitation requires concurrent requests from two different authenticated users or a specific timing window around the shared session restart; a single sequential request may not trigger the identity confusion.
  • PR:L assumes any authenticated user with chatbot access can trigger the issue; the patch does not evidence a higher privilege requirement.
  • VC:H assumes the data accessed (private cases, investigations) constitutes high confidentiality impact; the patch tests reference 'PRIVATE ADMIN INVESTIGATION' as the sensitive resource.
  • CAPEC-126 (Session Hijacking) is the closest available mapping but does not precisely describe a server-side shared-credential race; no CAPEC specifically covers multi-tenant credential isolation failures in a shared in-process session.
  • The affected version range is taken from the explicit analyst context (affected_version: 0, fixed_version: 4.1.0); the patch itself does not encode version boundaries.
  • No evidence of active exploitation, public PoC, or in-the-wild abuse is present in the patch or metadata.
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 6 11 medium 6
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-17 10:37 UTC Fix developed Corrective change authored (9eec395cc73c6706362b2c22f1e264406eb8caf8): fix: [security] Isolate chatbot MCP API identities https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8
  2. 2026-11-20 14:41 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133853",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:21:43.134744Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T16:33:24.293Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/chatbot/chatbot_core.py"
          ],
          "product": "flowintel",
          "programFiles": [
            "app/chatbot/chatbot_core.py"
          ],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThan": "4.1.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "FlowIntel\u0027s chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user\u0027s authenticated identity could be applied to another user\u0027s tool invocation, or a stale/ambient credential could be inherited by a new request.\n\nPreconditions:\n- An authenticated user with access to the chatbot interface.\n- Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user\u0027s credentials were written to the process environment.\n\nImpact:\n- A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases).\n- A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential.\n- The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface.\n\nAffected versions: FlowIntel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-126",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-126 Session Hijacking"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "HIGH",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 6,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE",
            "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-20T14:41:59Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-290",
              "description": "CWE-290 Authentication Bypass by Spoofing",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T14:44:31.341Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The shared persistent MCP session and process-wide API key mutation were removed. Each chatbot tool invocation now spawns its own short-lived MCP child process with credentials resolved fresh from the authenticated request context. If the user\u0027s identity or API key is unavailable, the invocation is rejected before any child process is launched, preventing fallback to ambient or stale credentials. Each transport is deterministically closed on success, failure, or timeout, eliminating residual credential exposure."
        }
      ],
      "title": "FlowIntel Chatbot Shared MCP Session Allows Cross-User API Identity Confusion",
      "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": [
                  "AC:H is assumed because reliable exploitation requires concurrent requests from two different authenticated users or a specific timing window around the shared session restart; a single sequential request may not trigger the identity confusion.",
                  "PR:L assumes any authenticated user with chatbot access can trigger the issue; the patch does not evidence a higher privilege requirement.",
                  "VC:H assumes the data accessed (private cases, investigations) constitutes high confidentiality impact; the patch tests reference \u0027PRIVATE ADMIN INVESTIGATION\u0027 as the sensitive resource.",
                  "CAPEC-126 (Session Hijacking) is the closest available mapping but does not precisely describe a server-side shared-credential race; no CAPEC specifically covers multi-tenant credential isolation failures in a shared in-process session.",
                  "The affected version range is taken from the explicit analyst context (affected_version: 0, fixed_version: 4.1.0); the patch itself does not encode version boundaries.",
                  "No evidence of active exploitation, public PoC, or in-the-wild abuse is present in the patch or metadata."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-126",
                    "rationale": "The closest available CAPEC. The shared MCP session acted as a single long-lived session whose credentials could be \u0027hijacked\u0027 by a concurrent request from a different user, causing the wrong identity to be used. No CAPEC specifically covers \u0027shared per-tenant credential state in a multi-user service,\u0027 so CAPEC-126 is the best approximation. Uncertainty: the attack does not involve a traditional network-level session token theft but rather a server-side shared-state race."
                  }
                ],
                "commit": "9eec395cc73c6706362b2c22f1e264406eb8caf8",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N: the chatbot is a network-accessible Flask endpoint. AC:H: exploitation requires concurrent or carefully timed requests from two different users to trigger the shared-session race, or a specific sequence of credential writes to the process environment. AT:N: no manipulation of a separate target is needed. PR:L: the attacker must be an authenticated user with chatbot access. UI:N: no victim interaction beyond their own request is required. VC:H: a user can read another user\u0027s sensitive data (private cases, investigations). VI:N, VA:N: no integrity or availability impact is evidenced. SC:N, SI:N, SA:N: no impact on separate components is demonstrated.",
                "fixSummary": "The shared persistent MCP session and process-wide API key mutation were removed. Each chatbot tool invocation now spawns its own short-lived MCP child process with credentials resolved fresh from the authenticated request context. If the user\u0027s identity or API key is unavailable, the invocation is rejected before any child process is launched, preventing fallback to ambient or stale credentials. Each transport is deterministically closed on success, failure, or timeout, eliminating residual credential exposure.",
                "generatedAt": "2026-11-20T14:41:59.093131Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 6,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "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": "b2eb7327abee28d605ef02f5af16f090ce7a643bd63bf2a5836e30539adfbb81",
                "patchSummary": "Removed the global _mcp_session, _mcp_loop, _mcp_thread, _mcp_current_api_key state and the _ensure_mcp() / _start_mcp_background() / _run_mcp_session() functions that maintained a single shared asyncio event loop and thread. Replaced with _mcp_environment() which resolves the user\u0027s API key from the authenticated session on every call and raises RuntimeError if unavailable, and _call_mcp_tool() which opens a per-invocation stdio transport, executes the tool, and closes the transport in all exit paths. Eliminated all os.environ mutations of FLOWINTEL_API_KEY. Added 33 regression tests in tests/chatbot/test_api_identity.py covering concurrent identity isolation, ambient-credential rejection, detached-user handling, key rotation, transport cleanup on failure/timeout, and real stdio child-process lifecycle.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "9eec395cc73c6706362b2c22f1e264406eb8caf8",
                    "date": "Tue, 17 Nov 2026 11:37:34 +0100",
                    "patchSha256": "b2eb7327abee28d605ef02f5af16f090ce7a643bd63bf2a5836e30539adfbb81",
                    "retrievedAt": "2026-11-20T14:41:10.165065Z",
                    "source": "https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8",
                    "subject": "fix: [security] Isolate chatbot MCP API identities"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T14:41:59Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Isolate chatbot MCP API identities",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-290",
                    "rationale": "The shared MCP session and process-wide environment variable allowed one user\u0027s authenticated identity (API key) to be applied to another user\u0027s tool invocation. The per-request identity was not isolated, effectively allowing identity confusion or spoofing between concurrent sessions."
                  },
                  {
                    "cweId": "CWE-200",
                    "rationale": "Because credentials were shared across requests and written to the process environment, a user could access data (e.g., private cases) belonging to another user whose key was cached in the shared session or ambient environment."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (9eec395cc73c6706362b2c22f1e264406eb8caf8): fix: [security] Isolate chatbot MCP API identities",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8"
                    ],
                    "timestamp": "2026-11-17T10:37:34Z",
                    "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/flowintel/flowintel/commit/9eec395cc73c6706362b2c22f1e264406eb8caf8"
                    ],
                    "timestamp": "2026-11-20T14:41:10.165065Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20421"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133853",
    "datePublished": "2026-11-20T14:44:31.341Z",
    "dateReserved": "2026-11-20T14:44:25.304Z",
    "dateUpdated": "2026-11-20T16:33:24.293Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Mitigation MIT-46
Architecture and Design

Strategy: Separation of Privilege

  • Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CAPEC-116: Excavation

An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes.

CAPEC-13: Subverting Environment Variable Values

The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary.

CAPEC-169: Footprinting

An adversary engages in probing and exploration activities to identify constituents and properties of the target.

CAPEC-22: Exploiting Trust in Client

An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.

CAPEC-224: Fingerprinting

An adversary compares output from a target system to known indicators that uniquely identify specific details about the target. Most commonly, fingerprinting is done to determine operating system and application versions. Fingerprinting can be done passively as well as actively. Fingerprinting by itself is not usually detrimental to the target. However, the information gathered through fingerprinting often enables an adversary to discover existing weaknesses in the target.

CAPEC-285: ICMP Echo Request Ping

An adversary sends out an ICMP Type 8 Echo Request, commonly known as a 'Ping', in order to determine if a target system is responsive. If the request is not blocked by a firewall or ACL, the target host will respond with an ICMP Type 0 Echo Reply datagram. This type of exchange is usually referred to as a 'Ping' due to the Ping utility present in almost all operating systems. Ping, as commonly implemented, allows a user to test for alive hosts, measure round-trip time, and measure the percentage of packet loss.

CAPEC-287: TCP SYN Scan

An adversary uses a SYN scan to determine the status of ports on the remote target. SYN scanning is the most common type of port scanning that is used because of its many advantages and few drawbacks. As a result, novice attackers tend to overly rely on the SYN scan while performing system reconnaissance. As a scanning method, the primary advantages of SYN scanning are its universality and speed.

CAPEC-290: Enumerate Mail Exchange (MX) Records

An adversary enumerates the MX records for a given via a DNS query. This type of information gathering returns the names of mail servers on the network. Mail servers are often not exposed to the Internet but are located within the DMZ of a network protected by a firewall. A side effect of this configuration is that enumerating the MX records for an organization my reveal the IP address of the firewall or possibly other internal systems. Attackers often resort to MX record enumeration when a DNS Zone Transfer is not possible.

CAPEC-291: DNS Zone Transfers

An attacker exploits a DNS misconfiguration that permits a ZONE transfer. Some external DNS servers will return a list of IP address and valid hostnames. Under certain conditions, it may even be possible to obtain Zone data about the organization's internal network. When successful the attacker learns valuable information about the topology of the target organization, including information about particular servers, their role within the IT structure, and possibly information about the operating systems running upon the network. This is configuration dependent behavior so it may also be required to search out multiple DNS servers while attempting to find one with ZONE transfers allowed.

CAPEC-292: Host Discovery

An adversary sends a probe to an IP address to determine if the host is alive. Host discovery is one of the earliest phases of network reconnaissance. The adversary usually starts with a range of IP addresses belonging to a target network and uses various methods to determine if a host is present at that IP address. Host discovery is usually referred to as 'Ping' scanning using a sonar analogy. The goal is to send a packet through to the IP address and solicit a response from the host. As such, a 'ping' can be virtually any crafted packet whatsoever, provided the adversary can identify a functional host based on its response. An attack of this nature is usually carried out with a 'ping sweep,' where a particular kind of ping is sent to a range of IP addresses.

CAPEC-293: Traceroute Route Enumeration

An adversary uses a traceroute utility to map out the route which data flows through the network in route to a target destination. Tracerouting can allow the adversary to construct a working topology of systems and routers by listing the systems through which data passes through on their way to the targeted machine. This attack can return varied results depending upon the type of traceroute that is performed. Traceroute works by sending packets to a target while incrementing the Time-to-Live field in the packet header. As the packet traverses each hop along its way to the destination, its TTL expires generating an ICMP diagnostic message that identifies where the packet expired. Traditional techniques for tracerouting involved the use of ICMP and UDP, but as more firewalls began to filter ingress ICMP, methods of traceroute using TCP were developed.

CAPEC-294: ICMP Address Mask Request

An adversary sends an ICMP Type 17 Address Mask Request to gather information about a target's networking configuration. ICMP Address Mask Requests are defined by RFC-950, "Internet Standard Subnetting Procedure." An Address Mask Request is an ICMP type 17 message that triggers a remote system to respond with a list of its related subnets, as well as its default gateway and broadcast address via an ICMP type 18 Address Mask Reply datagram. Gathering this type of information helps the adversary plan router-based attacks as well as denial-of-service attacks against the broadcast address.

CAPEC-295: Timestamp Request

This pattern of attack leverages standard requests to learn the exact time associated with a target system. An adversary may be able to use the timestamp returned from the target to attack time-based security algorithms, such as random number generators, or time-based authentication mechanisms.

CAPEC-296: ICMP Information Request

An adversary sends an ICMP Information Request to a host to determine if it will respond to this deprecated mechanism. ICMP Information Requests are a deprecated message type. Information Requests were originally used for diskless machines to automatically obtain their network configuration, but this message type has been superseded by more robust protocol implementations like DHCP.

CAPEC-297: TCP ACK Ping

An adversary sends a TCP segment with the ACK flag set to a remote host for the purpose of determining if the host is alive. This is one of several TCP 'ping' types. The RFC 793 expected behavior for a service is to respond with a RST 'reset' packet to any unsolicited ACK segment that is not part of an existing connection. So by sending an ACK segment to a port, the adversary can identify that the host is alive by looking for a RST packet. Typically, a remote server will respond with a RST regardless of whether a port is open or closed. In this way, TCP ACK pings cannot discover the state of a remote port because the behavior is the same in either case. The firewall will look up the ACK packet in its state-table and discard the segment because it does not correspond to any active connection. A TCP ACK Ping can be used to discover if a host is alive via RST response packets sent from the host.

CAPEC-298: UDP Ping

An adversary sends a UDP datagram to the remote host to determine if the host is alive. If a UDP datagram is sent to an open UDP port there is very often no response, so a typical strategy for using a UDP ping is to send the datagram to a random high port on the target. The goal is to solicit an 'ICMP port unreachable' message from the target, indicating that the host is alive. UDP pings are useful because some firewalls are not configured to block UDP datagrams sent to strange or typically unused ports, like ports in the 65K range. Additionally, while some firewalls may filter incoming ICMP, weaknesses in firewall rule-sets may allow certain types of ICMP (host unreachable, port unreachable) which are useful for UDP ping attempts.

CAPEC-299: TCP SYN Ping

An adversary uses TCP SYN packets as a means towards host discovery. Typical RFC 793 behavior specifies that when a TCP port is open, a host must respond to an incoming SYN "synchronize" packet by completing stage two of the 'three-way handshake' - by sending an SYN/ACK in response. When a port is closed, RFC 793 behavior is to respond with a RST "reset" packet. This behavior can be used to 'ping' a target to see if it is alive by sending a TCP SYN packet to a port and then looking for a RST or an ACK packet in response.

CAPEC-300: Port Scanning

An adversary uses a combination of techniques to determine the state of the ports on a remote target. Any service or application available for TCP or UDP networking will have a port open for communications over the network.

CAPEC-301: TCP Connect Scan

An adversary uses full TCP connection attempts to determine if a port is open on the target system. The scanning process involves completing a 'three-way handshake' with a remote port, and reports the port as closed if the full handshake cannot be established. An advantage of TCP connect scanning is that it works against any TCP/IP stack.

CAPEC-302: TCP FIN Scan

An adversary uses a TCP FIN scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with the FIN bit set in the packet header. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow the adversary to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.

CAPEC-303: TCP Xmas Scan

An adversary uses a TCP XMAS scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with all possible flags set in the packet header, generating packets that are illegal based on RFC 793. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow an attacker to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.

CAPEC-304: TCP Null Scan

An adversary uses a TCP NULL scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with no flags in the packet header, generating packets that are illegal based on RFC 793. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow an attacker to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.

CAPEC-305: TCP ACK Scan

An adversary uses TCP ACK segments to gather information about firewall or ACL configuration. The purpose of this type of scan is to discover information about filter configurations rather than port state. This type of scanning is rarely useful alone, but when combined with SYN scanning, gives a more complete picture of the type of firewall rules that are present.

CAPEC-306: TCP Window Scan

An adversary engages in TCP Window scanning to analyze port status and operating system type. TCP Window scanning uses the ACK scanning method but examine the TCP Window Size field of response RST packets to make certain inferences. While TCP Window Scans are fast and relatively stealthy, they work against fewer TCP stack implementations than any other type of scan. Some operating systems return a positive TCP window size when a RST packet is sent from an open port, and a negative value when the RST originates from a closed port. TCP Window scanning is one of the most complex scan types, and its results are difficult to interpret. Window scanning alone rarely yields useful information, but when combined with other types of scanning is more useful. It is a generally more reliable means of making inference about operating system versions than port status.

CAPEC-307: TCP RPC Scan

An adversary scans for RPC services listing on a Unix/Linux host.

CAPEC-308: UDP Scan

An adversary engages in UDP scanning to gather information about UDP port status on the target system. UDP scanning methods involve sending a UDP datagram to the target port and looking for evidence that the port is closed. Open UDP ports usually do not respond to UDP datagrams as there is no stateful mechanism within the protocol that requires building or establishing a session. Responses to UDP datagrams are therefore application specific and cannot be relied upon as a method of detecting an open port. UDP scanning relies heavily upon ICMP diagnostic messages in order to determine the status of a remote port.

CAPEC-309: Network Topology Mapping

An adversary engages in scanning activities to map network nodes, hosts, devices, and routes. Adversaries usually perform this type of network reconnaissance during the early stages of attack against an external network. Many types of scanning utilities are typically employed, including ICMP tools, network mappers, port scanners, and route testing utilities such as traceroute.

CAPEC-310: Scanning for Vulnerable Software

An attacker engages in scanning activity to find vulnerable software versions or types, such as operating system versions or network services. Vulnerable or exploitable network configurations, such as improperly firewalled systems, or misconfigured systems in the DMZ or external network, provide windows of opportunity for an attacker. Common types of vulnerable software include unpatched operating systems or services (e.g FTP, Telnet, SMTP, SNMP) running on open ports that the attacker has identified. Attackers usually begin probing for vulnerable software once the external network has been port scanned and potential targets have been revealed.

CAPEC-312: Active OS Fingerprinting

An adversary engages in activity to detect the operating system or firmware version of a remote target by interrogating a device, server, or platform with a probe designed to solicit behavior that will reveal information about the operating systems or firmware in the environment. Operating System detection is possible because implementations of common protocols (Such as IP or TCP) differ in distinct ways. While the implementation differences are not sufficient to 'break' compatibility with the protocol the differences are detectable because the target will respond in unique ways to specific probing activity that breaks the semantic or logical rules of packet construction for a protocol. Different operating systems will have a unique response to the anomalous input, providing the basis to fingerprint the OS behavior. This type of OS fingerprinting can distinguish between operating system types and versions.

CAPEC-313: Passive OS Fingerprinting

An adversary engages in activity to detect the version or type of OS software in a an environment by passively monitoring communication between devices, nodes, or applications. Passive techniques for operating system detection send no actual probes to a target, but monitor network or client-server communication between nodes in order to identify operating systems based on observed behavior as compared to a database of known signatures or values. While passive OS fingerprinting is not usually as reliable as active methods, it is generally better able to evade detection.

CAPEC-317: IP ID Sequencing Probe

This OS fingerprinting probe analyzes the IP 'ID' field sequence number generation algorithm of a remote host. Operating systems generate IP 'ID' numbers differently, allowing an attacker to identify the operating system of the host by examining how is assigns ID numbers when generating response packets. RFC 791 does not specify how ID numbers are chosen or their ranges, so ID sequence generation differs from implementation to implementation. There are two kinds of IP 'ID' sequence number analysis - IP 'ID' Sequencing: analyzing the IP 'ID' sequence generation algorithm for one protocol used by a host and Shared IP 'ID' Sequencing: analyzing the packet ordering via IP 'ID' values spanning multiple protocols, such as between ICMP and TCP.

CAPEC-318: IP 'ID' Echoed Byte-Order Probe

This OS fingerprinting probe tests to determine if the remote host echoes back the IP 'ID' value from the probe packet. An attacker sends a UDP datagram with an arbitrary IP 'ID' value to a closed port on the remote host to observe the manner in which this bit is echoed back in the ICMP error message. The identification field (ID) is typically utilized for reassembling a fragmented packet. Some operating systems or router firmware reverse the bit order of the ID field when echoing the IP Header portion of the original datagram within an ICMP error message.

CAPEC-319: IP (DF) 'Don't Fragment Bit' Echoing Probe

This OS fingerprinting probe tests to determine if the remote host echoes back the IP 'DF' (Don't Fragment) bit in a response packet. An attacker sends a UDP datagram with the DF bit set to a closed port on the remote host to observe whether the 'DF' bit is set in the response packet. Some operating systems will echo the bit in the ICMP error message while others will zero out the bit in the response packet.

CAPEC-320: TCP Timestamp Probe

This OS fingerprinting probe examines the remote server's implementation of TCP timestamps. Not all operating systems implement timestamps within the TCP header, but when timestamps are used then this provides the attacker with a means to guess the operating system of the target. The attacker begins by probing any active TCP service in order to get response which contains a TCP timestamp. Different Operating systems update the timestamp value using different intervals. This type of analysis is most accurate when multiple timestamp responses are received and then analyzed. TCP timestamps can be found in the TCP Options field of the TCP header.

CAPEC-321: TCP Sequence Number Probe

This OS fingerprinting probe tests the target system's assignment of TCP sequence numbers. One common way to test TCP Sequence Number generation is to send a probe packet to an open port on the target and then compare the how the Sequence Number generated by the target relates to the Acknowledgement Number in the probe packet. Different operating systems assign Sequence Numbers differently, so a fingerprint of the operating system can be obtained by categorizing the relationship between the acknowledgement number and sequence number as follows: 1) the Sequence Number generated by the target is Zero, 2) the Sequence Number generated by the target is the same as the acknowledgement number in the probe, 3) the Sequence Number generated by the target is the acknowledgement number plus one, or 4) the Sequence Number is any other non-zero number.

CAPEC-322: TCP (ISN) Greatest Common Divisor Probe

This OS fingerprinting probe sends a number of TCP SYN packets to an open port of a remote machine. The Initial Sequence Number (ISN) in each of the SYN/ACK response packets is analyzed to determine the smallest number that the target host uses when incrementing sequence numbers. This information can be useful for identifying an operating system because particular operating systems and versions increment sequence numbers using different values. The result of the analysis is then compared against a database of OS behaviors to determine the OS type and/or version.

CAPEC-323: TCP (ISN) Counter Rate Probe

This OS detection probe measures the average rate of initial sequence number increments during a period of time. Sequence numbers are incremented using a time-based algorithm and are susceptible to a timing analysis that can determine the number of increments per unit time. The result of this analysis is then compared against a database of operating systems and versions to determine likely operation system matches.

CAPEC-324: TCP (ISN) Sequence Predictability Probe

This type of operating system probe attempts to determine an estimate for how predictable the sequence number generation algorithm is for a remote host. Statistical techniques, such as standard deviation, can be used to determine how predictable the sequence number generation is for a system. This result can then be compared to a database of operating system behaviors to determine a likely match for operating system and version.

CAPEC-325: TCP Congestion Control Flag (ECN) Probe

This OS fingerprinting probe checks to see if the remote host supports explicit congestion notification (ECN) messaging. ECN messaging was designed to allow routers to notify a remote host when signal congestion problems are occurring. Explicit Congestion Notification messaging is defined by RFC 3168. Different operating systems and versions may or may not implement ECN notifications, or may respond uniquely to particular ECN flag types.

CAPEC-326: TCP Initial Window Size Probe

This OS fingerprinting probe checks the initial TCP Window size. TCP stacks limit the range of sequence numbers allowable within a session to maintain the "connected" state within TCP protocol logic. The initial window size specifies a range of acceptable sequence numbers that will qualify as a response to an ACK packet within a session. Various operating systems use different Initial window sizes. The initial window size can be sampled by establishing an ordinary TCP connection.

CAPEC-327: TCP Options Probe

This OS fingerprinting probe analyzes the type and order of any TCP header options present within a response segment. Most operating systems use unique ordering and different option sets when options are present. RFC 793 does not specify a required order when options are present, so different implementations use unique ways of ordering or structuring TCP options. TCP options can be generated by ordinary TCP traffic.

CAPEC-328: TCP 'RST' Flag Checksum Probe

This OS fingerprinting probe performs a checksum on any ASCII data contained within the data portion or a RST packet. Some operating systems will report a human-readable text message in the payload of a 'RST' (reset) packet when specific types of connection errors occur. RFC 1122 allows text payloads within reset packets but not all operating systems or routers implement this functionality.

CAPEC-329: ICMP Error Message Quoting Probe

An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the amount of data returned or "Quoted" from the originating request that generated the ICMP error message.

CAPEC-330: ICMP Error Message Echoing Integrity Probe

An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the integrity of data returned or "Quoted" from the originating request that generated the error message.

CAPEC-472: Browser Fingerprinting

An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.

CAPEC-497: File Discovery

An adversary engages in probing and exploration activities to determine if common key files exists. Such files often contain configuration and security parameters of the targeted application, system or network. Using this knowledge may often pave the way for more damaging attacks.

CAPEC-508: Shoulder Surfing

In a shoulder surfing attack, an adversary observes an unaware individual's keystrokes, screen content, or conversations with the goal of obtaining sensitive information. One motive for this attack is to obtain sensitive information about the target for financial, personal, political, or other gains. From an insider threat perspective, an additional motive could be to obtain system/application credentials or cryptographic keys. Shoulder surfing attacks are accomplished by observing the content "over the victim's shoulder", as implied by the name of this attack.

CAPEC-573: Process Footprinting

An adversary exploits functionality meant to identify information about the currently running processes on the target system to an authorized user. By knowing what processes are running on the target system, the adversary can learn about the target environment as a means towards further malicious behavior.

CAPEC-574: Services Footprinting

An adversary exploits functionality meant to identify information about the services on the target system to an authorized user. By knowing what services are registered on the target system, the adversary can learn about the target environment as a means towards further malicious behavior. Depending on the operating system, commands that can obtain services information include "sc" and "tasklist/svc" using Tasklist, and "net start" using Net.

CAPEC-575: Account Footprinting

An adversary exploits functionality meant to identify information about the domain accounts and their permissions on the target system to an authorized user. By knowing what accounts are registered on the target system, the adversary can inform further and more targeted malicious behavior. Example Windows commands which can acquire this information are: "net user" and "dsquery".

CAPEC-576: Group Permission Footprinting

An adversary exploits functionality meant to identify information about user groups and their permissions on the target system to an authorized user. By knowing what users/permissions are registered on the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command which can list local groups is "net localgroup".

CAPEC-577: Owner Footprinting

An adversary exploits functionality meant to identify information about the primary users on the target system to an authorized user. They may do this, for example, by reviewing logins or file modification times. By knowing what owners use the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command that may accomplish this is "dir /A ntuser.dat". Which will display the last modified time of a user's ntuser.dat file when run within the root folder of a user. This time is synonymous with the last time that user was logged in.

CAPEC-59: Session Credential Falsification through Prediction

This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.

CAPEC-60: Reusing Session IDs (aka Session Replay)

This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.

CAPEC-616: Establish Rogue Location

An adversary provides a malicious version of a resource at a location that is similar to the expected location of a legitimate resource. After establishing the rogue location, the adversary waits for a victim to visit the location and access the malicious resource.

CAPEC-643: Identify Shared Files/Directories on System

An adversary discovers connections between systems by exploiting the target system's standard practice of revealing them in searchable, common areas. Through the identification of shared folders/drives between systems, the adversary may further their goals of locating and collecting sensitive information/files, or map potential routes for lateral movement within the network.

CAPEC-646: Peripheral Footprinting

Adversaries may attempt to obtain information about attached peripheral devices and components connected to a computer system. Examples may include discovering the presence of iOS devices by searching for backups, analyzing the Windows registry to determine what USB devices have been connected, or infecting a victim system with malware to report when a USB device has been connected. This may allow the adversary to gain additional insight about the system or network environment, which may be useful in constructing further attacks.

CAPEC-651: Eavesdropping

An adversary intercepts a form of communication (e.g. text, audio, video) by way of software (e.g., microphone and audio recording application), hardware (e.g., recording equipment), or physical means (e.g., physical proximity). The goal of eavesdropping is typically to gain unauthorized access to sensitive information about the target for financial, personal, political, or other gains. Eavesdropping is different from a sniffing attack as it does not take place on a network-based communication channel (e.g., IP traffic). Instead, it entails listening in on the raw audio source of a conversation between two or more parties.

CAPEC-79: Using Slashes in Alternate Encoding

This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.