CVE-2026-133850 (GCVE-0-2026-133850)

Vulnerability from cvelistv5 – Published: 2026-11-20 14:39 – Updated: 2026-11-20 16:34
VLAI
Title
flowintel: Stale Authorization Allows Notification Disclosure After Case Access Revocation
Summary
flowintel contains an authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient's current access rights to that case before generating or displaying the notification. As a result, a user who previously had access to a private case and later had that access revoked can still: - Receive recurring reminder notifications containing case-related content. - View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case. The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time. Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch. 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:20 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 16:21 UTC
CWE
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 CPE status
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:20
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea 433c4d2d3f96…
Confidence
medium
Commit Subject Patch SHA-256
af6e91c8ac63 fix: [security] Recheck private case access for recurring 433c4d2d3f96…
Fix summary

The fix introduces an authorization re-check at two points: (1) before creating a recurring reminder notification, the system now verifies the recipient's current case visibility and skips delivery if access has been revoked; (2) when listing or counting stored notifications, the system now filters out case-related reminder notifications for which the viewing user no longer has case access. This ensures that both the creation and display paths enforce current authorization state rather than relying on a one-time check at subscription time.

Patch summary

In recurring_notification.py, the create_notification function now imports can_view_case and, for each recurring notification subscriber, fetches the User record and calls can_view_case(case, recipient); if the check fails, the notification is skipped via continue. In notification_core.py, the DEADLINE_ICONS tuple is extended to include the clock icon (fa-solid fa-clock), a new helper _is_case_deadline_notification is added to identify case-related deadline/reminder notifications by icon or notification_type, and _visible_deadline_notifications is updated to use this helper so that reminders for inaccessible cases are excluded from the returned list. The test file is updated to create a real Case object for the reminder notification fixture instead of using a hardcoded case_id.

CVSS rationale

AV:N: The application is a web-based platform accessed over the network. AC:L: No special race condition or complex setup is required; the user simply needs to have previously had case access and then have it revoked. AT:N: No manipulation of the target is needed. PR:L: An authenticated user with a valid account and prior case subscription is required. UI:N: Notifications are delivered and displayed automatically without requiring victim interaction. VC:L: Limited confidentiality impact; case-related notification content (titles, reminder messages) is exposed to a user who no longer has case access. VI:N, VA:N: No integrity or availability impact is evidenced. SC:N, SI:N, SA:N: The affected data resides within the same application scope; no cross-scope impact is indicated.

Weakness rationale
  • CWE-285 The system performed an authorization check at subscription time but failed to re-enforce it at notification delivery and display time. The authorization decision was not re-evaluated when the user's access to the case changed, resulting in continued access to case-related notification content. This is a failure to properly enforce authorization at the point of access rather than a complete absence of authorization logic.
  • CWE-862 In the recurring notification creation path, no authorization check existed at all before generating the notification for a subscriber. The check was entirely absent, not merely insufficient, making CWE-862 a defensible secondary mapping for the creation path specifically.
Attack pattern rationale
  • CAPEC-66 The notification subsystem operated with a lower security enforcement level than the case-access subsystem: it did not enforce the same access-control checks that governed case visibility. An attacker (or a user whose access was legitimately revoked) could exploit this misconfiguration to continue receiving case-related notification content. This is the closest CAPEC to the pattern of a component not enforcing the security level configured elsewhere in the application. The mapping is uncertain because no CAPEC specifically describes stale-authorization or missing re-authorization at delivery time; CAPEC-66 is selected as the best available match for a security-level enforcement gap between components.
Assumptions to verify
  • The affected version range is inferred from the explicit context (affected_version: 0, fixed_version: 4.1.0); the patch itself does not contain version strings.
  • The CAPEC-66 mapping is the closest available match; no CAPEC specifically covers stale-authorization or missing re-authorization at notification delivery time. This uncertainty is noted in the CAPEC rationale.
  • CVSS PR:L assumes the attacker is an authenticated user who previously had case access; the patch does not specify whether unauthenticated access is possible.
  • CVSS VC:L assumes the disclosed information is limited to notification content (case titles, reminder messages) rather than full case data; the patch only addresses notification visibility.
  • The patch does not indicate whether the vulnerability is exploitable remotely or requires local access; AV:N is assumed based on the web-application nature of the product.
  • The 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.
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 09:16 UTC Fix developed Corrective change authored (af6e91c8ac63c7ac0860325582bc2561ca5343ea): fix: [security] Recheck private case access for recurring https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea
  2. 2026-11-20 14:19 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133850",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:21:54.854825Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T16:34:25.206Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/bin/recurring_notification.py",
            "app/notification/notification_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 authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient\u0027s current access rights to that case before generating or displaying the notification.\n\nAs a result, a user who previously had access to a private case and later had that access revoked can still:\n- Receive recurring reminder notifications containing case-related content.\n- View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case.\n\nThe vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time.\n\nSecurity impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch.\n\nAffected versions: flowintel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-66",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-66 Exploiting Incorrectly Configured Security Levels"
            }
          ]
        }
      ],
      "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": "NONE",
            "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:N/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:20:25Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-285",
              "description": "CWE-285 Improper Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862 Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T14:39:48.936Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The fix introduces an authorization re-check at two points: (1) before creating a recurring reminder notification, the system now verifies the recipient\u0027s current case visibility and skips delivery if access has been revoked; (2) when listing or counting stored notifications, the system now filters out case-related reminder notifications for which the viewing user no longer has case access. This ensures that both the creation and display paths enforce current authorization state rather than relying on a one-time check at subscription time."
        }
      ],
      "title": "flowintel: Stale Authorization Allows Notification Disclosure After Case Access Revocation",
      "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 inferred from the explicit context (affected_version: 0, fixed_version: 4.1.0); the patch itself does not contain version strings.",
                  "The CAPEC-66 mapping is the closest available match; no CAPEC specifically covers stale-authorization or missing re-authorization at notification delivery time. This uncertainty is noted in the CAPEC rationale.",
                  "CVSS PR:L assumes the attacker is an authenticated user who previously had case access; the patch does not specify whether unauthenticated access is possible.",
                  "CVSS VC:L assumes the disclosed information is limited to notification content (case titles, reminder messages) rather than full case data; the patch only addresses notification visibility.",
                  "The patch does not indicate whether the vulnerability is exploitable remotely or requires local access; AV:N is assumed based on the web-application nature of the product.",
                  "The 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."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-66",
                    "rationale": "The notification subsystem operated with a lower security enforcement level than the case-access subsystem: it did not enforce the same access-control checks that governed case visibility. An attacker (or a user whose access was legitimately revoked) could exploit this misconfiguration to continue receiving case-related notification content. This is the closest CAPEC to the pattern of a component not enforcing the security level configured elsewhere in the application. The mapping is uncertain because no CAPEC specifically describes stale-authorization or missing re-authorization at delivery time; CAPEC-66 is selected as the best available match for a security-level enforcement gap between components."
                  }
                ],
                "commit": "af6e91c8ac63c7ac0860325582bc2561ca5343ea",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N: The application is a web-based platform accessed over the network. AC:L: No special race condition or complex setup is required; the user simply needs to have previously had case access and then have it revoked. AT:N: No manipulation of the target is needed. PR:L: An authenticated user with a valid account and prior case subscription is required. UI:N: Notifications are delivered and displayed automatically without requiring victim interaction. VC:L: Limited confidentiality impact; case-related notification content (titles, reminder messages) is exposed to a user who no longer has case access. VI:N, VA:N: No integrity or availability impact is evidenced. SC:N, SI:N, SA:N: The affected data resides within the same application scope; no cross-scope impact is indicated.",
                "fixSummary": "The fix introduces an authorization re-check at two points: (1) before creating a recurring reminder notification, the system now verifies the recipient\u0027s current case visibility and skips delivery if access has been revoked; (2) when listing or counting stored notifications, the system now filters out case-related reminder notifications for which the viewing user no longer has case access. This ensures that both the creation and display paths enforce current authorization state rather than relying on a one-time check at subscription time.",
                "generatedAt": "2026-11-20T14:20:25.637194Z",
                "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": "433c4d2d3f9663b3d5b556b1d1236ba7ada4e9ef128b0cca9f53b69d8d1a0e1c",
                "patchSummary": "In recurring_notification.py, the create_notification function now imports can_view_case and, for each recurring notification subscriber, fetches the User record and calls can_view_case(case, recipient); if the check fails, the notification is skipped via continue. In notification_core.py, the DEADLINE_ICONS tuple is extended to include the clock icon (fa-solid fa-clock), a new helper _is_case_deadline_notification is added to identify case-related deadline/reminder notifications by icon or notification_type, and _visible_deadline_notifications is updated to use this helper so that reminders for inaccessible cases are excluded from the returned list. The test file is updated to create a real Case object for the reminder notification fixture instead of using a hardcoded case_id.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "af6e91c8ac63c7ac0860325582bc2561ca5343ea",
                    "date": "Tue, 17 Nov 2026 10:16:17 +0100",
                    "patchSha256": "433c4d2d3f9663b3d5b556b1d1236ba7ada4e9ef128b0cca9f53b69d8d1a0e1c",
                    "retrievedAt": "2026-11-20T14:19:53.580074Z",
                    "source": "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea",
                    "subject": "fix: [security] Recheck private case access for recurring"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T14:20:25Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Recheck private case access for recurring",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-285",
                    "rationale": "The system performed an authorization check at subscription time but failed to re-enforce it at notification delivery and display time. The authorization decision was not re-evaluated when the user\u0027s access to the case changed, resulting in continued access to case-related notification content. This is a failure to properly enforce authorization at the point of access rather than a complete absence of authorization logic."
                  },
                  {
                    "cweId": "CWE-862",
                    "rationale": "In the recurring notification creation path, no authorization check existed at all before generating the notification for a subscriber. The check was entirely absent, not merely insufficient, making CWE-862 a defensible secondary mapping for the creation path specifically."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (af6e91c8ac63c7ac0860325582bc2561ca5343ea): fix: [security] Recheck private case access for recurring",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea"
                    ],
                    "timestamp": "2026-11-17T09:16:17Z",
                    "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/af6e91c8ac63c7ac0860325582bc2561ca5343ea"
                    ],
                    "timestamp": "2026-11-20T14:19:53.580074Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20418"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133850",
    "datePublished": "2026-11-20T14:39:48.936Z",
    "dateReserved": "2026-11-20T14:39:45.487Z",
    "dateUpdated": "2026-11-20T16:34:25.206Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "cpes": [
                  "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
                ],
                "modules": [
                  "app/bin/recurring_notification.py",
                  "app/notification/notification_core.py"
                ],
                "product": "flowintel",
                "repo": "https://github.com/flowintel/flowintel",
                "vendor": "flowintel",
                "versions": [
                  {
                    "lessThan": "4.1.0",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "flowintel contains an authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient\u0027s current access rights to that case before generating or displaying the notification.\n\nAs a result, a user who previously had access to a private case and later had that access revoked can still:\n- Receive recurring reminder notifications containing case-related content.\n- View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case.\n\nThe vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time.\n\nSecurity impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch.\n\nAffected versions: flowintel prior to 4.1.0."
          }
        ],
        "id": "CVE-2026-133850",
        "lastModified": "2026-11-20T17:18:22.880",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "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:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "ssvcData": {
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "Supplier",
                "timestamp": "2026-11-20T14:20:25Z",
                "version": "2.0.3"
              }
            },
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-133850",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:21:54.854825Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-20T15:17:53.323",
        "references": [
          {
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "url": "https://github.com/flowintel/flowintel/commit/af6e91c8ac63c7ac0860325582bc2561ca5343ea"
          }
        ],
        "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-285"
              },
              {
                "lang": "en",
                "value": "CWE-862"
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}


Solutions

CNA · CIRCL
The fix introduces an authorization re-check at two points: (1) before creating a recurring reminder notification, the system now verifies the recipient's current case visibility and skips delivery if access has been revoked; (2) when listing or counting stored notifications, the system now filters out case-related reminder notifications for which the viewing user no longer has case access. This ensures that both the creation and display paths enforce current authorization state rather than relying on a one-time check at subscription time.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.