CWE-668
Weakness DiscouragedExposure of Resource to Wrong Sphere
Abstraction: Class · Status: Draft
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files.
A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system.
In either case, the end result is that a resource has been exposed to the wrong party.
Mapping guidance
CWE-668 is high-level and is often misused as a catch-all when lower-level children might be applicable. It is sometimes used for low-information vulnerability reports [REF-1287]. It is a level-1 Class (i.e., a child of a Pillar). It is not useful for trend analysis.
Frequent misuse appears to be related to access control issues (poor authorization (CWE-285) or authentication (CWE-287)); insertion of sensitive information (CWE-201) or improper removal of sensitive information (CWE-212); insecure permissions (CWE-732 and descendants); or others. Closely analyze the specific mistake that is allowing the resource to be exposed, and perform a CWE mapping for that mistake. It is highly likely that CWE-668's children or descendants could apply.
Modes of introduction
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Notes
Theoretical
A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.
Content history
updated Time_of_Introduction
updated Relationships, Other_Notes
updated Relationships
updated Relationships
Clarified description to include permissions.
updated Description, Relationships
updated Other_Notes, Theoretical_Notes
updated Relationships
updated Relationships
updated Relationships
updated Common_Consequences
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Modes_of_Introduction, Relationships, Relevant_Properties
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated References
updated Relationships
updated Mapping_Notes
updated Common_Consequences, Relationships
updated Applicable_Platforms, Relationships, Weakness_Ordinalities
updated Mapping_Notes
updated Mapping_Notes, Relationships
1335 vulnerabilities reference this CWE, most recent first.
CVE-2026-133844 (GCVE-0-2026-133844)
Vulnerability from cvelistv5 – Published: 2026-11-20 14:38 – Updated: 2026-11-20 16:35| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/2ff… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-20 14:28 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416
49d10b72d8d9… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
2ff99ca6ed81
|
fix: [security] Filter case connector metadata by viewer | 49d10b72d8d9… |
Fix summary
The fix introduces viewer-scoped authorization checks during case serialization. Connector instances are now filtered based on the acting user's permissions: administrators and assigned case-administrators retain full visibility, while regular users only see connectors whose sharing scope (personal, org, or global) grants them access. When no authenticated user context is available, connector metadata is omitted entirely. Credential-use checks for module execution remain unchanged.
Patch summary
In app/db_class/db.py, the to_json method's connector serialization was changed from an unconditional query of all Case_Connector_Instance records to a conditional block that: (1) returns an empty list if user is None or unauthenticated; (2) imports can_access_all_case_connectors and is_instance_visible_to_user; (3) filters the connector list so only instances passing the visibility predicate are serialized. A new test file tests/case/test_case_connector_visibility.py (250 lines, 22 tests) validates API responses, browser views, Matrix delegation, scope changes, access revocation, fork behavior, and module-context credential isolation.
CVSS rationale
AV:N - exploitable over the network via standard API or browser endpoints. AC:L - no special conditions; any case view triggers the disclosure. AT:N - no attack-target manipulation required. PR:L - requires a low-privilege authenticated user with case read access. UI:N - no victim interaction beyond the attacker's own request. VC:L - limited confidential data (connector URLs, descriptions, UUIDs, possibly API keys) is exposed. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary-system impact evidenced.
Weakness rationale
- CWE-668 Connector metadata belonging to one user or organization (personal or org scope) was exposed to users in a different sphere (other users, other organizations) because the serialization path lacked per-viewer authorization filtering.
- CWE-862 The to_json serialization method did not perform any authorization check on connector instances before including them in the response, effectively missing the access-control gate that should restrict visibility to the acting user.
Attack pattern rationale
- CAPEC-1 The closest plausible CAPEC is Software Feature Discovery: an authenticated user can enumerate connector instances attached to a case and learn their URLs, descriptions, UUIDs, and potentially credentials that were not intended for their access level. The attack is passive (simply viewing a case) and requires no special tooling. Uncertainty: no CAPEC specifically models 'viewing an object to discover embedded metadata of other tenants'; CAPEC-1 is the best available match for unauthorized information enumeration through a legitimate interface.
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 encode version boundaries.
- PR:L assumes the attacker needs only a low-privilege authenticated account with case read access; the patch does not specify whether anonymous access to case endpoints is possible, but the fix explicitly omits connectors when user is None, implying unauthenticated access to the case object may exist.
- VC:L assumes the exposed connector metadata (URLs, descriptions, UUIDs, possibly API keys) constitutes limited but meaningful confidential information; the tests reference 'DO-NOT-EXPOSE-GLOBAL-KEY' and 'DO-NOT-EXPOSE-PERSONAL-KEY' suggesting credentials may be present in connector metadata.
- CAPEC-1 is selected as the closest available attack pattern; no CAPEC precisely models cross-tenant metadata leakage through a legitimate read endpoint.
- The commit message references 'Tool: Codex' which is noted as the AI tool used to generate the patch but is not credited as a vulnerability finder or reporter.
- 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 |
- 2026-11-16 06:56 UTC Fix developed Corrective change authored (2ff99ca6ed81687fe28d57961d158e0804271416): fix: [security] Filter case connector metadata by viewer https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416
- 2026-11-20 14:27 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133844",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T16:20:43.125388Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T16:35:25.063Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/db_class/db.py (Case.to_json)"
],
"product": "flowintel",
"programFiles": [
"app/db_class/db.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, a threat intelligence case management platform, contains an information disclosure vulnerability in its case serialization logic. When a case is rendered via the REST API or browser views, all connector instances associated with that case were included in the response regardless of the requesting user\u0027s permissions.\n\nThis means that any authenticated user with read access to a case could observe connector metadata belonging to other users (personal-scope connectors) or other organizations (org-scope connectors), including connector URLs, descriptions, UUIDs, and potentially embedded API credentials.\n\nPreconditions:\n- An authenticated user account with at least read access to the affected case\n- The case must have connector instances attached that belong to other users or organizations\n\nImpact:\n- Disclosure of personal connector endpoints and credentials of other users\n- Disclosure of organization-scoped connector metadata across organizational boundaries\n- Enumeration of connector infrastructure (URLs, UUIDs, descriptions) not intended for the viewer\n\nAffected versions: \u003c 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-1 Software Feature 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": "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:28:25Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T14:38:14.992Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces viewer-scoped authorization checks during case serialization. Connector instances are now filtered based on the acting user\u0027s permissions: administrators and assigned case-administrators retain full visibility, while regular users only see connectors whose sharing scope (personal, org, or global) grants them access. When no authenticated user context is available, connector metadata is omitted entirely. Credential-use checks for module execution remain unchanged."
}
],
"title": "FlowIntel Case Serialization Exposes Unauthorized Connector Metadata to Authenticated Users",
"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 \u00270\u0027, fixed_version \u00274.1.0\u0027); the patch itself does not encode version boundaries.",
"PR:L assumes the attacker needs only a low-privilege authenticated account with case read access; the patch does not specify whether anonymous access to case endpoints is possible, but the fix explicitly omits connectors when user is None, implying unauthenticated access to the case object may exist.",
"VC:L assumes the exposed connector metadata (URLs, descriptions, UUIDs, possibly API keys) constitutes limited but meaningful confidential information; the tests reference \u0027DO-NOT-EXPOSE-GLOBAL-KEY\u0027 and \u0027DO-NOT-EXPOSE-PERSONAL-KEY\u0027 suggesting credentials may be present in connector metadata.",
"CAPEC-1 is selected as the closest available attack pattern; no CAPEC precisely models cross-tenant metadata leakage through a legitimate read endpoint.",
"The commit message references \u0027Tool: Codex\u0027 which is noted as the AI tool used to generate the patch but is not credited as a vulnerability finder or reporter.",
"No evidence of active exploitation, public PoC, or in-the-wild abuse is present in the patch or metadata."
],
"capecRationale": [
{
"capecId": "CAPEC-1",
"rationale": "The closest plausible CAPEC is Software Feature Discovery: an authenticated user can enumerate connector instances attached to a case and learn their URLs, descriptions, UUIDs, and potentially credentials that were not intended for their access level. The attack is passive (simply viewing a case) and requires no special tooling. Uncertainty: no CAPEC specifically models \u0027viewing an object to discover embedded metadata of other tenants\u0027; CAPEC-1 is the best available match for unauthorized information enumeration through a legitimate interface."
}
],
"commit": "2ff99ca6ed81687fe28d57961d158e0804271416",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N - exploitable over the network via standard API or browser endpoints. AC:L - no special conditions; any case view triggers the disclosure. AT:N - no attack-target manipulation required. PR:L - requires a low-privilege authenticated user with case read access. UI:N - no victim interaction beyond the attacker\u0027s own request. VC:L - limited confidential data (connector URLs, descriptions, UUIDs, possibly API keys) is exposed. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary-system impact evidenced.",
"fixSummary": "The fix introduces viewer-scoped authorization checks during case serialization. Connector instances are now filtered based on the acting user\u0027s permissions: administrators and assigned case-administrators retain full visibility, while regular users only see connectors whose sharing scope (personal, org, or global) grants them access. When no authenticated user context is available, connector metadata is omitted entirely. Credential-use checks for module execution remain unchanged.",
"generatedAt": "2026-11-20T14:28:25.634529Z",
"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": "49d10b72d8d9897080d70c3317449db9c0f785d9a8fe2614858da3dffab0b1ba",
"patchSummary": "In app/db_class/db.py, the to_json method\u0027s connector serialization was changed from an unconditional query of all Case_Connector_Instance records to a conditional block that: (1) returns an empty list if user is None or unauthenticated; (2) imports can_access_all_case_connectors and is_instance_visible_to_user; (3) filters the connector list so only instances passing the visibility predicate are serialized. A new test file tests/case/test_case_connector_visibility.py (250 lines, 22 tests) validates API responses, browser views, Matrix delegation, scope changes, access revocation, fork behavior, and module-context credential isolation.",
"patchTruncated": false,
"patches": [
{
"commit": "2ff99ca6ed81687fe28d57961d158e0804271416",
"date": "Mon, 16 Nov 2026 07:56:14 +0100",
"patchSha256": "49d10b72d8d9897080d70c3317449db9c0f785d9a8fe2614858da3dffab0b1ba",
"retrievedAt": "2026-11-20T14:27:54.587830Z",
"source": "https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416",
"subject": "fix: [security] Filter case connector metadata by viewer"
}
],
"source": "https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T14:28:25Z",
"version": "2.0.3"
},
"subject": "fix: [security] Filter case connector metadata by viewer",
"weaknessRationale": [
{
"cweId": "CWE-668",
"rationale": "Connector metadata belonging to one user or organization (personal or org scope) was exposed to users in a different sphere (other users, other organizations) because the serialization path lacked per-viewer authorization filtering."
},
{
"cweId": "CWE-862",
"rationale": "The to_json serialization method did not perform any authorization check on connector instances before including them in the response, effectively missing the access-control gate that should restrict visibility to the acting user."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (2ff99ca6ed81687fe28d57961d158e0804271416): fix: [security] Filter case connector metadata by viewer",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/2ff99ca6ed81687fe28d57961d158e0804271416"
],
"timestamp": "2026-11-16T06:56:14Z",
"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/2ff99ca6ed81687fe28d57961d158e0804271416"
],
"timestamp": "2026-11-20T14:27:54.587830Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20413"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133844",
"datePublished": "2026-11-20T14:38:14.992Z",
"dateReserved": "2026-11-20T14:38:10.738Z",
"dateUpdated": "2026-11-20T16:35:25.063Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133001 (GCVE-0-2026-133001)
Vulnerability from cvelistv5 – Published: 2026-11-19 10:35 – Updated: 2026-11-19 17:16| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/c15… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-18 14:20 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
408047b5b5e0… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
c158e1bdcebd
|
fix: [security] Refresh alert ownership scope on duplicate | 408047b5b5e0… |
Fix summary
The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert's review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector's scope has been narrowed or reassigned.
Patch summary
In app/alerting/alerting_core.py, within the _update_existing_alert function, two lines were added before the terminal-review-status conditional block: existing.owner_user_id and existing.owner_org_id are now assigned from the normalized incoming data on every duplicate update. Previously these fields were only set during initial alert creation and were not refreshed when a duplicate alert was ingested, leaving the stale scope in place.
CVSS rationale
AV:N - the platform is network-accessible. AC:L - the vulnerability is inherent in the duplicate-update code path; no special race or timing is needed. AT:N - no manipulation of the attack target is required. PR:L - an authenticated user with prior access to the alert is needed. UI:N - no user interaction beyond normal platform use. VC:L - confidential alert data is exposed to users outside the intended scope, but only for alerts affected by a scope change. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary impacts. The overall severity is moderate: limited to a subset of alerts whose scope changed, requiring prior legitimate access.
Weakness rationale
- CWE-668 The alert resource remains exposed to a broader set of users/organizations (the wrong sphere) because the ownership/visibility fields are not updated when the connector scope changes. The resource is accessible to entities outside its intended authorization boundary.
- CWE-862 The system fails to enforce the current authorization scope on duplicate updates, effectively missing the authorization check that would restrict visibility to the correct set of users and organizations.
Attack pattern rationale
- CAPEC-10 The closest plausible attack pattern is leveraging a trusted relationship: a user or organization that previously had legitimate access to an alert (because it was within their scope) retains that access after the scope should have been narrowed. The attacker leverages the stale trust/visibility binding. This mapping is uncertain because the vulnerability is more of a stale-state authorization bug than an active exploitation of trust, but CAPEC-10 is the best available match for unauthorized access via a previously valid relationship.
Assumptions to verify
- The affected version range is not precisely specified in the patch metadata; the affected_version field contains '0' which is treated as a placeholder. All versions prior to commit c158e1bd are assumed affected.
- The CAPEC-10 mapping is the closest available match but the vulnerability is more accurately described as a stale-state authorization defect rather than an active exploitation of trust relationships.
- The severity of the confidentiality impact (VC:L) assumes that the exposed alert content is sensitive but that the exposure is limited to a subset of alerts whose scope changed; if all alerts are affected or contain highly sensitive data, VC could be rated Higher.
- The platform is assumed to be a multi-tenant or multi-organization security alerting system where visibility scoping is a core authorization mechanism.
- No evidence of active exploitation or public PoC was found 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 |
7 | 11 | medium | 5 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362): fix: [security] Refresh alert ownership scope on duplicate https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
- 2026-11-18 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133001",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T17:16:15.912845Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:16:23.842Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/alerting/alerting_core.py"
],
"product": "flowintel",
"programFiles": [
"app/alerting/alerting_core.py"
],
"repo": "https://github.com/flowintel/flowintel",
"vendor": "flowintel",
"versions": [
{
"lessThanOrEqual": "4.0.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": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector\u0027s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector\u0027s scope was narrowed or changed.\n\nThis means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: \u003c4.1.0."
}
],
"impacts": [
{
"capecId": "CAPEC-10",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-10 Leveraging Trusted Relationships"
}
]
}
],
"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-18T14:20:42Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T10:35:06.740Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert\u0027s review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector\u0027s scope has been narrowed or reassigned."
}
],
"title": "FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion",
"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 not precisely specified in the patch metadata; the affected_version field contains \u00270\u0027 which is treated as a placeholder. All versions prior to commit c158e1bd are assumed affected.",
"The CAPEC-10 mapping is the closest available match but the vulnerability is more accurately described as a stale-state authorization defect rather than an active exploitation of trust relationships.",
"The severity of the confidentiality impact (VC:L) assumes that the exposed alert content is sensitive but that the exposure is limited to a subset of alerts whose scope changed; if all alerts are affected or contain highly sensitive data, VC could be rated Higher.",
"The platform is assumed to be a multi-tenant or multi-organization security alerting system where visibility scoping is a core authorization mechanism.",
"No evidence of active exploitation or public PoC was found in the patch or metadata."
],
"capecRationale": [
{
"capecId": "CAPEC-10",
"rationale": "The closest plausible attack pattern is leveraging a trusted relationship: a user or organization that previously had legitimate access to an alert (because it was within their scope) retains that access after the scope should have been narrowed. The attacker leverages the stale trust/visibility binding. This mapping is uncertain because the vulnerability is more of a stale-state authorization bug than an active exploitation of trust, but CAPEC-10 is the best available match for unauthorized access via a previously valid relationship."
}
],
"commit": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N - the platform is network-accessible. AC:L - the vulnerability is inherent in the duplicate-update code path; no special race or timing is needed. AT:N - no manipulation of the attack target is required. PR:L - an authenticated user with prior access to the alert is needed. UI:N - no user interaction beyond normal platform use. VC:L - confidential alert data is exposed to users outside the intended scope, but only for alerts affected by a scope change. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary impacts. The overall severity is moderate: limited to a subset of alerts whose scope changed, requiring prior legitimate access.",
"fixSummary": "The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert\u0027s review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector\u0027s scope has been narrowed or reassigned.",
"generatedAt": "2026-11-18T14:20:42.931868Z",
"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": "408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d",
"patchSummary": "In app/alerting/alerting_core.py, within the _update_existing_alert function, two lines were added before the terminal-review-status conditional block: existing.owner_user_id and existing.owner_org_id are now assigned from the normalized incoming data on every duplicate update. Previously these fields were only set during initial alert creation and were not refreshed when a duplicate alert was ingested, leaving the stale scope in place.",
"patchTruncated": false,
"patches": [
{
"commit": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362",
"date": "Fri, 6 Nov 2026 10:54:31 +0100",
"patchSha256": "408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d",
"retrievedAt": "2026-11-18T14:20:07.629180Z",
"source": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"subject": "fix: [security] Refresh alert ownership scope on duplicate"
}
],
"source": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:20:42Z",
"version": "2.0.3"
},
"subject": "fix: [security] Refresh alert ownership scope on duplicate",
"weaknessRationale": [
{
"cweId": "CWE-668",
"rationale": "The alert resource remains exposed to a broader set of users/organizations (the wrong sphere) because the ownership/visibility fields are not updated when the connector scope changes. The resource is accessible to entities outside its intended authorization boundary."
},
{
"cweId": "CWE-862",
"rationale": "The system fails to enforce the current authorization scope on duplicate updates, effectively missing the authorization check that would restrict visibility to the correct set of users and organizations."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362): fix: [security] Refresh alert ownership scope on duplicate",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"
],
"timestamp": "2026-11-06T09:54:31Z",
"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/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"
],
"timestamp": "2026-11-18T14:20:07.629180Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20317"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133001",
"datePublished": "2026-11-19T10:35:06.740Z",
"dateReserved": "2026-11-19T10:34:56.100Z",
"dateUpdated": "2026-11-19T17:16:23.842Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130770 (GCVE-0-2026-130770)
Vulnerability from cvelistv5 – Published: 2026-11-18 19:02 – Updated: 2026-11-18 19:02- CWE-668 - Exposure of Resource to Wrong Sphere
| URL | Tags |
|---|---|
| https://github.com/lxc/incus/security/advisories/… | vendor-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/lxc/incus/v7/cmd/incusd",
"product": "incus",
"vendor": "lxc",
"versions": [
{
"lessThan": "7.6.0",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "7.6.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "stgraber"
}
],
"datePublic": "2026-10-29T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Incus before 7.6.0 creates the NBD servers used for virtual machine migration and disk export on abstract unix sockets, which have no permission checks and whose names are visible in /proc/net/unix. A local unprivileged user can connect while an operation runs to read or modify the VM disk, gaining code execution in the guest on a migration\u0027s receiving side."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "LOCAL",
"baseScore": 9.2,
"baseSeverity": "CRITICAL",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 8.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T19:02:47.117Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-3rgf-297m-775x)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/lxc/incus/security/advisories/GHSA-3rgf-297m-775x"
}
],
"title": "Incus before 7.6.0 VM Disk Hijacking via Abstract NBD Unix Sockets",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-130770",
"datePublished": "2026-11-18T19:02:47.117Z",
"dateReserved": "2026-11-17T15:43:21.185Z",
"dateUpdated": "2026-11-18T19:02:47.117Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-128118 (GCVE-0-2026-128118)
Vulnerability from cvelistv5 – Published: 2026-11-13 19:31 – Updated: 2026-11-18 04:12| URL | Tags |
|---|---|
| https://github.com/sveltejs/kit/security/advisori… | x_refsource_CONFIRM |
| https://github.com/sveltejs/kit/commit/ae07803806… | x_refsource_MISC |
| https://github.com/sveltejs/kit/releases/tag/@sve… | x_refsource_MISC |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-128118",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T04:12:28.354460Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T04:12:42.242Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "kit",
"vendor": "sveltejs",
"versions": [
{
"status": "affected",
"version": "\u003e= 3.0.0, \u003c 3.1.1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From version 3.0.0 until 3.1.1, the build-time server-only module guard did not treat src/params.js as a client entry point even though parameter matchers can run in the browser. Server-only modules imported through src/params.js could consequently enter the client bundle, where statically replaced private environment values or other server secrets could be exposed. This issue is fixed in 3.1.1."
}
],
"metrics": [
{
"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"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668: Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-13T19:31:04.678Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/sveltejs/kit/security/advisories/GHSA-m9j8-jcmv-hp69",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/sveltejs/kit/security/advisories/GHSA-m9j8-jcmv-hp69"
},
{
"name": "https://github.com/sveltejs/kit/commit/ae07803806f75b8b5662ae4ab92934ca1356fd84",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/sveltejs/kit/commit/ae07803806f75b8b5662ae4ab92934ca1356fd84"
},
{
"name": "https://github.com/sveltejs/kit/releases/tag/@sveltejs/kit@3.1.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/sveltejs/kit/releases/tag/@sveltejs/kit@3.1.1"
}
],
"source": {
"advisory": "GHSA-m9j8-jcmv-hp69",
"discovery": "UNKNOWN"
},
"title": "SvelteKit: Build-time server-only module import guard could fail, resulting in server secrets being statically replaced in client bundle"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-128118",
"datePublished": "2026-11-13T19:31:04.678Z",
"dateReserved": "2026-11-12T22:42:47.031Z",
"dateUpdated": "2026-11-18T04:12:42.242Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-120308 (GCVE-0-2026-120308)
Vulnerability from cvelistv5 – Published: 2026-11-01 12:51 – Updated: 2026-11-02 19:45| URL | Tags |
|---|---|
| https://github.com/beam-cloud/beta9 | product |
| https://github.com/beam-cloud/beta9/pull/1897 | patch |
| https://github.com/beam-cloud/beta9/commit/a28bf1… | patch |
| https://github.com/beam-cloud/beta9/releases/tag/… | release-notes |
| https://github.com/beam-cloud/beta9/releases/tag/… | release-notes |
| https://github.com/beam-cloud/beta9/releases/tag/… | technical-description |
| https://github.com/beam-cloud/beta9/releases/tag/… | technical-description |
| Vendor | Product | Version | |
|---|---|---|---|
| beam-cloud | Beta9 gateway |
Affected:
0 , < 0.1.776
(semver)
|
|
| beam-cloud | Beta9 worker |
Affected:
0 , < 0.1.756
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-120308",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-02T19:45:04.950921Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T19:45:15.233Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://github.com/beam-cloud/beta9/releases",
"defaultStatus": "unaffected",
"packageName": "github.com/beam-cloud/beta9",
"product": "Beta9 gateway",
"programFiles": [
"pkg/abstractions/common/mount.go",
"pkg/gateway/services/stub.go"
],
"repo": "git://github.com/beam-cloud/beta9",
"vendor": "beam-cloud",
"versions": [
{
"lessThan": "0.1.776",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com/beam-cloud/beta9/releases",
"defaultStatus": "unaffected",
"packageName": "github.com/beam-cloud/beta9",
"product": "Beta9 worker",
"programFiles": [
"pkg/abstractions/common/mount.go",
"pkg/worker/lifecycle.go"
],
"repo": "git://github.com/beam-cloud/beta9",
"vendor": "beam-cloud",
"versions": [
{
"lessThan": "0.1.756",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Natan Nehorai"
},
{
"lang": "en",
"type": "coordinator",
"value": "JFrog Security Research"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker\u0027s filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker\u0027s files, including other tenants\u0027 volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.\u003c/p\u003e"
}
],
"value": "A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker\u0027s filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker\u0027s files, including other tenants\u0027 volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.9,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "Tenant with a workspace token deploying a function that attaches a volume"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-22",
"description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668: Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-01T12:51:50.481Z",
"orgId": "48a46f29-ae42-4e1d-90dd-c1676c1e5e6d",
"shortName": "JFROG"
},
"references": [
{
"name": "Beta9 repository",
"tags": [
"product"
],
"url": "https://github.com/beam-cloud/beta9"
},
{
"name": "Handle sandbox edge cases (fix pull request)",
"tags": [
"patch"
],
"url": "https://github.com/beam-cloud/beta9/pull/1897"
},
{
"name": "Fix commit a28bf12",
"tags": [
"patch"
],
"url": "https://github.com/beam-cloud/beta9/commit/a28bf12cf0007c792a25d8ed282b4e8bf6f30393"
},
{
"name": "gateway-0.1.776",
"tags": [
"release-notes"
],
"url": "https://github.com/beam-cloud/beta9/releases/tag/gateway-0.1.776"
},
{
"name": "worker-0.1.756",
"tags": [
"release-notes"
],
"url": "https://github.com/beam-cloud/beta9/releases/tag/worker-0.1.756"
},
{
"name": "gateway-0.1.769 (confirmed affected)",
"tags": [
"technical-description"
],
"url": "https://github.com/beam-cloud/beta9/releases/tag/gateway-0.1.769"
},
{
"name": "worker-0.1.745 (confirmed affected)",
"tags": [
"technical-description"
],
"url": "https://github.com/beam-cloud/beta9/releases/tag/worker-0.1.745"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later. Volume identifiers and mount paths are rejected when they are empty, \".\", \"..\", or contain a slash (identifiers) or a \"..\" segment (mount paths). The gateway also refuses a volume the workspace does not own. Stubs stored before the check existed are validated when they are launched. The fix is commit a28bf12 (pull request 1897), released on 2026-09-15.\u003c/p\u003e"
}
],
"value": "Upgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later. Volume identifiers and mount paths are rejected when they are empty, \".\", \"..\", or contain a slash (identifiers) or a \"..\" segment (mount paths). The gateway also refuses a volume the workspace does not own. Stubs stored before the check existed are validated when they are launched. The fix is commit a28bf12 (pull request 1897), released on 2026-09-15."
}
],
"source": {
"discovery": "EXTERNAL"
},
"timeline": [
{
"lang": "en",
"time": "2026-09-07T02:47:00.000Z",
"value": "Confirmed affected releases worker-0.1.745 and gateway-0.1.769 are current"
},
{
"lang": "en",
"time": "2026-09-15T04:03:00.000Z",
"value": "Fix merged in pull request 1897 (commit a28bf12)"
},
{
"lang": "en",
"time": "2026-09-15T04:04:00.000Z",
"value": "Fixed releases worker-0.1.756 and gateway-0.1.776 published. No vendor security advisory was filed with the pull request."
}
],
"title": "Beta9 host filesystem exposure via volume path traversal",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "48a46f29-ae42-4e1d-90dd-c1676c1e5e6d",
"assignerShortName": "JFROG",
"cveId": "CVE-2026-120308",
"datePublished": "2026-11-01T12:51:50.481Z",
"dateReserved": "2026-11-01T12:46:51.095Z",
"dateUpdated": "2026-11-02T19:45:15.233Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-119726 (GCVE-0-2026-119726)
Vulnerability from cvelistv5 – Published: 2026-11-17 16:23 – Updated: 2026-11-17 16:57| Vendor | Product | Version | |
|---|---|---|---|
| PocketBook / Obreey Products | PocketBook Reader |
Affected:
5.65.0.39561.release (com.obreey.reader)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-119726",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:57:03.438129Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:57:22.852Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/migros/migros-security-advisories/blob/main/advisories/msec-2026-007_pocketbook-app_remote-path-traversal-leaking-credentials-through-http-server.md"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"platforms": [
"Android"
],
"product": "PocketBook Reader",
"vendor": "PocketBook / Obreey Products",
"versions": [
{
"status": "affected",
"version": "5.65.0.39561.release (com.obreey.reader)"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027) vulnerability in PocketBook / Obreey Products PocketBook Reader (Android) allows Exposure of Sensitive Information to an Unauthorized Actor.\u003cp\u003eThis issue affects PocketBook Reader (Android): 5.65.0.39561.release (com.obreey.reader).\u003c/p\u003e"
}
],
"value": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027) vulnerability in PocketBook / Obreey Products PocketBook Reader (Android) allows Exposure of Sensitive Information to an Unauthorized Actor.\n\nThis issue affects PocketBook Reader (Android): 5.65.0.39561.release (com.obreey.reader)."
}
],
"impacts": [
{
"descriptions": [
{
"lang": "en",
"value": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-22",
"description": "CWE-22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:23:46.786Z",
"orgId": "455daabc-a392-441d-aa46-37d35189897c",
"shortName": "NCSC.ch"
},
"references": [
{
"url": "https://github.com/migros/migros-security-advisories/blob/main/advisories/msec-2026-007_pocketbook-app_remote-path-traversal-leaking-credentials-through-http-server.md"
},
{
"url": "https://play.google.com/store/apps/details?id=com.obreey.reader"
}
],
"source": {
"advisory": "MSEC-2026-007",
"discovery": "EXTERNAL"
},
"title": "PocketBook Reader Android App - Remote Path Traversal Allows Arbitrary File Read and Credential Theft",
"x_generator": {
"engine": "Vulnogram 0.1.0-dev"
}
}
},
"cveMetadata": {
"assignerOrgId": "455daabc-a392-441d-aa46-37d35189897c",
"assignerShortName": "NCSC.ch",
"cveId": "CVE-2026-119726",
"datePublished": "2026-11-17T16:23:46.786Z",
"dateReserved": "2026-10-30T15:04:28.908Z",
"dateUpdated": "2026-11-17T16:57:22.852Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-118410 (GCVE-0-2026-118410)
Vulnerability from cvelistv5 – Published: 2026-11-11 12:40 – Updated: 2026-11-17 15:34- CWE-668 - Exposure of Resource to Wrong Sphere
| URL | Tags |
|---|---|
| https://github.com/apache/roller/pull/226 | patch |
| https://lists.apache.org/thread/oy4wv2d7sy9p9kl9n… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| Apache Software Foundation | Apache Roller |
Affected:
4.0 , ≤ 6.1.6
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-118410",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T15:34:27.412087Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T15:34:46.377Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unknown",
"product": "Apache Roller",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThanOrEqual": "6.1.6",
"status": "affected",
"version": "4.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "hataehoon (GitHub: dpfkdlemtp)"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Exposure of Resource to Wrong Sphere in Apache Roller 4.0 through 6.1.6 allows an unauthenticated visitor to read an entry after its author has withdrawn it to draft through the AtomPub API. The entry was removed from the weblog but stayed in the search index, and public search showed its content. AtomPub is disabled by default. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which shows only published entries in search results."
}
],
"value": "Exposure of Resource to Wrong Sphere in Apache Roller 4.0 through 6.1.6 allows an unauthenticated visitor to read an entry after its author has withdrawn it to draft through the AtomPub API. The entry was removed from the weblog but stayed in the search index, and public search showed its content. AtomPub is disabled by default. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which shows only published entries in search results."
}
],
"metrics": [
{
"other": {
"content": {
"text": "Low"
},
"type": "Textual description of severity"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.7,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668: Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-11T12:40:00.215Z",
"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"shortName": "apache"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/apache/roller/pull/226"
},
{
"tags": [
"vendor-advisory"
],
"url": "https://lists.apache.org/thread/oy4wv2d7sy9p9kl9nnvvfsjlgsk8bnco"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Apache Roller: Unpublished entries remain readable through search after AtomPub unpublish",
"x_generator": {
"engine": "Vulnogram 1.0.3"
}
}
},
"cveMetadata": {
"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"assignerShortName": "apache",
"cveId": "CVE-2026-118410",
"datePublished": "2026-11-11T12:40:00.215Z",
"dateReserved": "2026-10-28T03:33:56.038Z",
"dateUpdated": "2026-11-17T15:34:46.377Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-115522 (GCVE-0-2026-115522)
Vulnerability from cvelistv5 – Published: 2026-10-28 04:36 – Updated: 2026-11-05 17:01- CWE-668 - Exposure of Resource to Wrong Sphere
| URL | Tags |
|---|---|
| https://github.com/google/adk-python/issues/5618 | issue-trackingexploit |
| https://github.com/google/adk-python/pull/5619 | patch |
| https://github.com/google/adk-python/commit/f72f0… | patch |
| https://github.com/google/adk-python/commit/c27d8… | patch |
| https://github.com/google/adk-python/commit/0ae2b… | patch |
| https://github.com/google/adk-python/releases/tag… | release-notes |
| https://github.com/google/adk-python/releases/tag… | release-notes |
| Vendor | Product | Version | |
|---|---|---|---|
| Agent Development Kit (ADK) for Python |
Affected:
1.19.0 , < 1.39.1
(semver)
Affected: 2.0.0a1 , < 2.7.0 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-115522",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-05T17:00:45.990624Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-05T17:01:12.141Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageName": "google-adk",
"product": "Agent Development Kit (ADK) for Python",
"repo": "https://github.com/google/adk-python",
"vendor": "Google",
"versions": [
{
"lessThan": "1.39.1",
"status": "affected",
"version": "1.19.0",
"versionType": "semver"
},
{
"lessThan": "2.7.0",
"status": "affected",
"version": "2.0.0a1",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "@Nant361"
}
],
"datePublic": "2026-07-29T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eExposure of Resource to Wrong Sphere (CWE-668) in \u003ccode\u003eFileArtifactService\u003c/code\u003e in Google Agent Development Kit (ADK) for Python (\u003ccode\u003egoogle-adk\u003c/code\u003e) versions 1.19.0 before 1.39.1 and 2.0.0a1 before 2.7.0 allows a caller in one application to list, read, overwrite, or delete artifacts belonging to another application when both applications share a \u003ccode\u003eFileArtifactService\u003c/code\u003e root directory and use the same \u003ccode\u003euser_id\u003c/code\u003e (and \u003ccode\u003esession_id\u003c/code\u003e for session-scoped artifacts). \u003ccode\u003eFileArtifactService\u003c/code\u003e accepted \u003ccode\u003eapp_name\u003c/code\u003e across its public API methods but omitted \u003ccode\u003eapp_name\u003c/code\u003e when constructing on-disk paths (\u003ccode\u003eroot/users/{user_id}/...\u003c/code\u003e instead of \u003ccode\u003eroot/apps/{app_name}/users/{user_id}/...\u003c/code\u003e). Version 2.6.0 scoped writes by \u003ccode\u003eapp_name\u003c/code\u003e but retained a legacy \u003ccode\u003eroot/users/{user_id}\u003c/code\u003e fallback for reads and deletes; version 2.7.0 and the 1.x backport in version 1.39.1 removed the fallback and enforce full per-app path scoping.\u003c/p\u003e"
}
],
"value": "Exposure of Resource to Wrong Sphere (CWE-668) in FileArtifactService in Google Agent Development Kit (ADK) for Python (google-adk) versions 1.19.0 before 1.39.1 and 2.0.0a1 before 2.7.0 allows a caller in one application to list, read, overwrite, or delete artifacts belonging to another application when both applications share a FileArtifactService root directory and use the same user_id (and session_id for session-scoped artifacts). FileArtifactService accepted app_name across its public API methods but omitted app_name when constructing on-disk paths (root/users/{user_id}/... instead of root/apps/{app_name}/users/{user_id}/...). Version 2.6.0 scoped writes by app_name but retained a legacy root/users/{user_id} fallback for reads and deletes; version 2.7.0 and the 1.x backport in version 1.39.1 removed the fallback and enforce full per-app path scoping."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT: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",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T04:36:49.927Z",
"orgId": "14ed7db2-1595-443d-9d34-6215bf890778",
"shortName": "Google"
},
"references": [
{
"tags": [
"issue-tracking",
"exploit"
],
"url": "https://github.com/google/adk-python/issues/5618"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/pull/5619"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/f72f0db58c5c1f4e8b8d4f04b8c592c9e49cbe9e"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/c27d8688ed9ea619587ad96cbfd641c34dd7340c"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/0ae2bffdd2628af6c8643bc4fd40c2f49f0c6bd4"
},
{
"tags": [
"release-notes"
],
"url": "https://github.com/google/adk-python/releases/tag/v1.39.1"
},
{
"tags": [
"release-notes"
],
"url": "https://github.com/google/adk-python/releases/tag/v2.7.0"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade Google Agent Development Kit (ADK) for Python (\u003ccode\u003egoogle-adk\u003c/code\u003e) to version 1.39.1 (for 1.x installations) or version 2.7.0 (for 2.x installations) or later.\u003c/p\u003e"
}
],
"value": "Upgrade Google Agent Development Kit (ADK) for Python (google-adk) to version 1.39.1 (for 1.x installations) or version 2.7.0 (for 2.x installations) or later."
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Cross-Application Artifact Namespace Isolation in Google Agent Development Kit (ADK) for Python",
"x_generator": {
"engine": "Vulnogram 1.0.2"
}
}
},
"cveMetadata": {
"assignerOrgId": "14ed7db2-1595-443d-9d34-6215bf890778",
"assignerShortName": "Google",
"cveId": "CVE-2026-115522",
"datePublished": "2026-10-28T04:36:49.927Z",
"dateReserved": "2026-10-22T18:18:29.284Z",
"dateUpdated": "2026-11-05T17:01:12.141Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-112936 (GCVE-0-2026-112936)
Vulnerability from cvelistv5 – Published: 2026-10-20 14:34 – Updated: 2026-10-20 16:47| URL | Tags |
|---|---|
| https://github.com/tox-dev/filelock/security/advi… | x_refsource_CONFIRM |
| https://github.com/tox-dev/filelock/commit/4d45e8… | x_refsource_MISC |
| https://github.com/tox-dev/filelock/releases/tag/4.0.9 | x_refsource_MISC |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112936",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-20T16:47:15.788698Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-20T16:47:39.872Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "filelock",
"vendor": "tox-dev",
"versions": [
{
"status": "affected",
"version": "\u003e= 3.20.4, \u003c 4.0.9"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory to redirect database creation and locking or split mutual exclusion between targets. This issue is fixed in version 4.0.9."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "LOW",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-59",
"description": "CWE-59: Improper Link Resolution Before File Access (\u0027Link Following\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668: Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-20T14:34:47.210Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56"
},
{
"name": "https://github.com/tox-dev/filelock/commit/4d45e83caf7e31f9a12fb44526bdc07f70114f04",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/tox-dev/filelock/commit/4d45e83caf7e31f9a12fb44526bdc07f70114f04"
},
{
"name": "https://github.com/tox-dev/filelock/releases/tag/4.0.9",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/tox-dev/filelock/releases/tag/4.0.9"
}
],
"source": {
"advisory": "GHSA-j8f7-rjxc-mr56",
"discovery": "UNKNOWN"
},
"title": "filelock: ReadWriteLock follows a symlink at the lock path into SQLite"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-112936",
"datePublished": "2026-10-20T14:34:47.210Z",
"dateReserved": "2026-10-19T21:30:47.244Z",
"dateUpdated": "2026-10-20T16:47:39.872Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-112185 (GCVE-0-2026-112185)
Vulnerability from cvelistv5 – Published: 2026-11-10 16:58 – Updated: 2026-11-16 17:02| Vendor | Product | Version | |
|---|---|---|---|
| Eclipse Foundation | Eclipse Kura |
Affected:
5.1.0 , ≤ 5.6.2
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112185",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T17:00:10.493401Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T17:02:40.608Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Eclipse Kura",
"vendor": "Eclipse Foundation",
"versions": [
{
"lessThanOrEqual": "5.6.2",
"status": "affected",
"version": "5.1.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIn Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not restrict access to the configuration of the UserAdmin persistence component to identities holding the kura.admin permission. An authenticated identity holding only the rest.configuration permission can read the password hashes of all identities, including administrators, which are stored as unsalted SHA-256 digests. The same identity can also modify identities and permission assignments, and restore previous configuration snapshots, which allows escalation to full administrative privileges. The issue is fixed in Eclipse Kura 5.6.3.\u003c/p\u003e"
}
],
"value": "In Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not restrict access to the configuration of the UserAdmin persistence component to identities holding the kura.admin permission. An authenticated identity holding only the rest.configuration permission can read the password hashes of all identities, including administrators, which are stored as unsalted SHA-256 digests. The same identity can also modify identities and permission assignments, and restore previous configuration snapshots, which allows escalation to full administrative privileges. The issue is fixed in Eclipse Kura 5.6.3."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "HIGH",
"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:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-863",
"description": "CWE-863",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T16:58:30.765Z",
"orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"shortName": "eclipse"
},
"references": [
{
"url": "https://github.com/eclipse-kura/kura/security/advisories/GHSA-gqr7-j252-qwqx"
},
{
"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430"
}
],
"source": {
"discovery": "UNKNOWN"
},
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"assignerShortName": "eclipse",
"cveId": "CVE-2026-112185",
"datePublished": "2026-11-10T16:58:30.765Z",
"dateReserved": "2026-10-19T09:21:00.410Z",
"dateUpdated": "2026-11-16T17:02:40.608Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.