CWE-522
Weakness Allowed-with-ReviewInsufficiently Protected Credentials
Abstraction: Class · Status: Incomplete
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Mapping guidance
This CWE entry is a Class and might have Base-level children that would be more appropriate
Examine children of this entry to see if there is a better fit
Relationships and members
Modes of introduction
COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
Detection methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Content history
updated Potential_Mitigations, Time_of_Introduction
updated Relationships, Other_Notes, Taxonomy_Mappings
updated Related_Attack_Patterns
updated Relationships
updated Common_Consequences
updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Related_Attack_Patterns, Relationships
updated Demonstrative_Examples, Potential_Mitigations
updated Other_Notes, Relationships
updated Relationships
updated Related_Attack_Patterns
updated Demonstrative_Examples, Modes_of_Introduction, Relationships, Taxonomy_Mappings
updated Relationships
updated Related_Attack_Patterns
updated Related_Attack_Patterns, Relationships
updated Description, Relationships, Type
updated Related_Attack_Patterns, Relationships
updated Demonstrative_Examples
updated Relationships
updated Relationships
updated Demonstrative_Examples, Observed_Examples, References, Relationships
updated Applicable_Platforms, Observed_Examples, Relationships
updated Detection_Factors, Relationships
updated Mapping_Notes
updated Observed_Examples
updated Applicable_Platforms, Relationships, Weakness_Ordinalities
2256 vulnerabilities reference this CWE, most recent first.
CVE-2026-134350 (GCVE-0-2026-134350)
Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34- CWE-522 - Insufficiently Protected Credentials
| URL | Tags |
|---|---|
| https://github.com/rclone/rclone/security/advisor… | vendor-advisory |
| https://www.vulncheck.com/advisories/rclone-1.67.… | third-party-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/rclone/rclone",
"product": "rclone",
"vendor": "rclone",
"versions": [
{
"lessThan": "1.76.0",
"status": "affected",
"version": "1.67.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "1.76.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*",
"versionEndExcluding": "1.76.0",
"versionStartIncluding": "1.67.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "remediation developer",
"value": "ncw"
},
{
"lang": "en",
"type": "finder",
"value": "manus-use"
}
],
"datePublic": "2026-11-06T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "rclone 1.67.0 before 1.76.0 contains a credential leak vulnerability in the Ulozto backend that sends X-Auth-Token and X-User-Token headers to unintended hosts on HTTP redirect because downloads use the authenticated f.rest client instead of f.cdn. Attackers who can observe or redirect CDN download traffic can capture the long-lived API key and session token to gain persistent access to the victim\u0027s Ulozto storage."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T16:34:30.558Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-3xpx-hjg2-vrjh)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/rclone/rclone/security/advisories/GHSA-3xpx-hjg2-vrjh"
},
{
"name": "VulnCheck Advisory: rclone 1.67.0 before 1.76.0 Auth Token Leak via Ulozto Backend Redirect",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/rclone-1.67.0-before-1.76.0-auth-token-leak-via-ulozto-backend-redirect"
}
],
"title": "rclone 1.67.0 before 1.76.0 Auth Token Leak via Ulozto Backend Redirect",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-134350",
"datePublished": "2026-11-21T16:34:30.558Z",
"dateReserved": "2026-11-21T00:00:14.018Z",
"dateUpdated": "2026-11-21T16:34:30.558Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133630 (GCVE-0-2026-133630)
Vulnerability from cvelistv5 – Published: 2026-11-20 09:09 – Updated: 2026-11-20 18:17| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/6b2… | 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 09:03 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch
6cdbee24e7fd… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
6b26b3f8cf9f
|
fix: [security] Keep checkout credentials out of Docker build | 6cdbee24e7fd… |
Fix summary
The checkout step is configured to not persist credentials into the workspace, and the full branch history is fetched during the authenticated checkout phase. This ensures the job token is never written to the Git configuration file that enters the Docker build context, eliminating the credential from build cache layers while preserving the ability to resolve release tags against the main branch.
Patch summary
In .github/workflows/docker.yml, the actions/checkout@v4 step is updated with persist-credentials: false to prevent the job token from being stored in .git/config, and fetch-depth: 0 to retrieve full history during the authenticated checkout. The subsequent git fetch origin main command in the branch-check step is removed since the origin/main reference is already available locally from the full-depth checkout.
CVSS rationale
AV:L: Exploitation requires local access to the CI/CD build environment or exported build cache; it is not remotely exploitable over a network. AC:L: Once build cache access is obtained, extracting the token from .git/config is straightforward. AT:N: No active user interaction is required. PR:H: The attacker needs high privileges (access to the CI/CD build infrastructure or build cache storage). UI:N: No user interaction is needed. VC/VI/VA:N: The CI/CD system itself is not directly compromised. SC:H: The exposed token grants full read access to the private repository, a separate system. SI:N: The job token typically has read-only scope by default; no evidence of write access. SA:N: No availability impact on the secondary system.
Weakness rationale
- CWE-522 The GitHub Actions job token (a bearer credential) was persisted in .git/config and included in the Docker build context and cache layers without being removed, constituting insufficient protection of credentials in a build artifact.
- CWE-200 The credential was exposed in Docker build cache layers accessible to anyone with access to the build environment, constituting information disclosure of a sensitive authentication token.
Attack pattern rationale
- CAPEC-1 The closest plausible CAPEC is Session Hijacking: the exposed job token functions as a bearer credential that, if obtained from the build cache, allows an attacker to impersonate the CI/CD system's authenticated session and access the private repository. This is an imperfect mapping because the token is a CI/CD job token rather than a user session cookie, but the underlying mechanism (stealing a valid credential to assume an authenticated identity) aligns with the CAPEC-1 pattern. No CAPEC specifically covers credential leakage in build artifacts, so CAPEC-1 is the best available match.
Assumptions to verify
- The GitHub Actions job token has read-only scope to the repository by default; if write scope is configured, SI could be elevated to Low.
- The build cache is accessible to a limited set of actors (CI/CD operators or platform administrators); broader exposure (e.g., public Docker registry with cached layers) would change AV and PR ratings.
- CAPEC-1 (Session Hijacking) is the closest available mapping; no CAPEC specifically addresses credential leakage in CI/CD build artifacts.
- The affected version range is inferred from the explicit context (affected_version: 0, fixed_version: 4.1.0); the exact first vulnerable release is not confirmed by the patch alone.
- The vulnerability is specific to the GitHub Actions Docker build workflow and does not affect the flowintel application runtime.
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-03 12:17 UTC Fix developed Corrective change authored (6b26b3f8cf9fab13244d1496443f822114ce4d05): fix: [security] Keep checkout credentials out of Docker build https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch
- 2026-11-20 09:02 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133630",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:16:56.116043Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:17:10.037Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
".github/workflows/docker.yml"
],
"product": "flowintel",
"programFiles": [
".github/workflows/docker.yml"
],
"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": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "The flowintel Docker build workflow used the GitHub Actions checkout action with default credential persistence, causing the job authentication token to be written into the repository\u0027s Git configuration file. This file became part of the Docker build context and could be retained in exported build cache layers, even though Git metadata was stripped from the final runtime image.\n\nAn attacker with access to the CI/CD build cache or build environment could extract the persisted token and use it to gain unauthorized access to the private source repository.\n\nImpact:\n- Exposure of a valid authentication token to the private repository\n- Potential unauthorized read access to source code and repository metadata\n\nAffected versions: flowintel \u003c 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-1 Session Hijacking"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "LOCAL",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "HIGH",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T09:03:23Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522 Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T09:09:40.890Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05"
}
],
"solutions": [
{
"lang": "en",
"value": "The checkout step is configured to not persist credentials into the workspace, and the full branch history is fetched during the authenticated checkout phase. This ensures the job token is never written to the Git configuration file that enters the Docker build context, eliminating the credential from build cache layers while preserving the ability to resolve release tags against the main branch."
}
],
"title": "flowintel CI/CD Workflow Exposes Checkout Credentials in Docker Build Cache",
"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 GitHub Actions job token has read-only scope to the repository by default; if write scope is configured, SI could be elevated to Low.",
"The build cache is accessible to a limited set of actors (CI/CD operators or platform administrators); broader exposure (e.g., public Docker registry with cached layers) would change AV and PR ratings.",
"CAPEC-1 (Session Hijacking) is the closest available mapping; no CAPEC specifically addresses credential leakage in CI/CD build artifacts.",
"The affected version range is inferred from the explicit context (affected_version: 0, fixed_version: 4.1.0); the exact first vulnerable release is not confirmed by the patch alone.",
"The vulnerability is specific to the GitHub Actions Docker build workflow and does not affect the flowintel application runtime."
],
"capecRationale": [
{
"capecId": "CAPEC-1",
"rationale": "The closest plausible CAPEC is Session Hijacking: the exposed job token functions as a bearer credential that, if obtained from the build cache, allows an attacker to impersonate the CI/CD system\u0027s authenticated session and access the private repository. This is an imperfect mapping because the token is a CI/CD job token rather than a user session cookie, but the underlying mechanism (stealing a valid credential to assume an authenticated identity) aligns with the CAPEC-1 pattern. No CAPEC specifically covers credential leakage in build artifacts, so CAPEC-1 is the best available match."
}
],
"commit": "6b26b3f8cf9fab13244d1496443f822114ce4d05",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:L: Exploitation requires local access to the CI/CD build environment or exported build cache; it is not remotely exploitable over a network. AC:L: Once build cache access is obtained, extracting the token from .git/config is straightforward. AT:N: No active user interaction is required. PR:H: The attacker needs high privileges (access to the CI/CD build infrastructure or build cache storage). UI:N: No user interaction is needed. VC/VI/VA:N: The CI/CD system itself is not directly compromised. SC:H: The exposed token grants full read access to the private repository, a separate system. SI:N: The job token typically has read-only scope by default; no evidence of write access. SA:N: No availability impact on the secondary system.",
"fixSummary": "The checkout step is configured to not persist credentials into the workspace, and the full branch history is fetched during the authenticated checkout phase. This ensures the job token is never written to the Git configuration file that enters the Docker build context, eliminating the credential from build cache layers while preserving the ability to resolve release tags against the main branch.",
"generatedAt": "2026-11-20T09:03:23.235755Z",
"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": "6cdbee24e7fdf8bec92a1ccaa19b9f8c7fbf5229080dfb4029456b9fe84cf493",
"patchSummary": "In .github/workflows/docker.yml, the actions/checkout@v4 step is updated with persist-credentials: false to prevent the job token from being stored in .git/config, and fetch-depth: 0 to retrieve full history during the authenticated checkout. The subsequent git fetch origin main command in the branch-check step is removed since the origin/main reference is already available locally from the full-depth checkout.",
"patchTruncated": false,
"patches": [
{
"commit": "6b26b3f8cf9fab13244d1496443f822114ce4d05",
"date": "Tue, 3 Nov 2026 13:17:37 +0100",
"patchSha256": "6cdbee24e7fdf8bec92a1ccaa19b9f8c7fbf5229080dfb4029456b9fe84cf493",
"retrievedAt": "2026-11-20T09:02:44.223116Z",
"source": "https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch",
"subject": "fix: [security] Keep checkout credentials out of Docker build"
}
],
"source": "https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T09:03:23Z",
"version": "2.0.3"
},
"subject": "fix: [security] Keep checkout credentials out of Docker build",
"weaknessRationale": [
{
"cweId": "CWE-522",
"rationale": "The GitHub Actions job token (a bearer credential) was persisted in .git/config and included in the Docker build context and cache layers without being removed, constituting insufficient protection of credentials in a build artifact."
},
{
"cweId": "CWE-200",
"rationale": "The credential was exposed in Docker build cache layers accessible to anyone with access to the build environment, constituting information disclosure of a sensitive authentication token."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (6b26b3f8cf9fab13244d1496443f822114ce4d05): fix: [security] Keep checkout credentials out of Docker build",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch"
],
"timestamp": "2026-11-03T12:17:37Z",
"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/6b26b3f8cf9fab13244d1496443f822114ce4d05.patch"
],
"timestamp": "2026-11-20T09:02:44.223116Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20377"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133630",
"datePublished": "2026-11-20T09:09:40.890Z",
"dateReserved": "2026-11-20T09:09:38.574Z",
"dateUpdated": "2026-11-20T18:17:10.037Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133613 (GCVE-0-2026-133613)
Vulnerability from cvelistv5 – Published: 2026-11-20 07:38 – Updated: 2026-11-20 18:07| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/607… | 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 06:54 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch
08c621737fc4… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
607e23000ea3
|
fix: [security] Pass community data API keys outside child | 08c621737fc4… |
Fix summary
The launcher no longer forwards the admin API key in the child process command line. The key is now passed exclusively through the FLOWINTEL_ADMIN_API_KEY environment variable, which is not visible in process listings. A hidden terminal prompt (read -r -s) is provided for interactive use, and the Python helper reads the key from the environment by default. Legacy positional and --api-key argument forms remain functional for backward compatibility but emit a warning documenting the exposure risk.
Patch summary
launch.sh: Added a read_admin_api_key function that resolves the key from the FLOWINTEL_ADMIN_API_KEY environment variable, a hidden terminal prompt, or a legacy positional argument (with a warning). The test_data_community and delete_test_data_community functions now export the key as FLOWINTEL_ADMIN_API_KEY in the child environment instead of passing it as --api-key on the command line. init_community_data.py: Changed --api-key from required=True to default=os.environ.get('FLOWINTEL_ADMIN_API_KEY'), added a parser.error() guard when no key is available, and updated docstrings. README.md and doc/user-manual.md: Updated usage examples to remove the positional key argument and document the environment-variable and hidden-prompt workflows.
CVSS rationale
AV:L: The attacker must have local access to the host to read process arguments. AC:L: Reading process arguments via ps or /proc is trivial and requires no special conditions. AT:N: No data tampering is needed. PR:N: Any local user can read process arguments; no elevated privileges are required. UI:N: The attacker does not need victim interaction beyond the victim running the launcher. VC/VI/VA:N: The vulnerable component (launcher script) itself is not directly compromised. SC/SI/SA:H: The exposed admin API key grants full administrative access to the Flowintel REST API (a separate component), allowing complete read, write, and delete of all threat intelligence data, users, and configurations.
Weakness rationale
- CWE-200 The admin API key is placed in process arguments (argv), which are readable by all local users via ps or /proc/<pid>/cmdline. This exposes a sensitive credential to unauthorized local actors.
- CWE-522 The credential (admin API key) is transmitted between the launcher and the helper process in a manner that does not protect it from local observation, failing to adequately safeguard the credential in transit.
Attack pattern rationale
- CAPEC-66 The system places the API key in a context (process arguments) that is assumed to be private, but on multi-user Unix systems process arguments are visible to all local users. The attacker exploits this trust assumption by reading the key from the process table. This is the closest available CAPEC; no CAPEC specifically covers local process-argument sniffing, so CAPEC-66 is selected as the best approximation of exploiting a trusted-context assumption in an untrusted context.
Assumptions to verify
- The affected version range is not explicitly stated in the patch; all versions prior to commit 607e23000ea39172ccff4d0de1fb1b7026c795c4 are assumed affected.
- The Flowintel REST API is assumed to be a separate component from the launcher script, justifying scope change (SC/SI/SA) in the CVSS vector.
- The CAPEC-66 mapping is approximate; no CAPEC specifically covers local process-argument information disclosure, so the closest plausible pattern was selected.
- PR:N assumes any unprivileged local user can read process arguments; on systems with restricted /proc access, PR may need to be raised.
- The exposure window is limited to the duration of the helper process execution, but this is sufficient for a local attacker to capture the key.
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 (607e23000ea39172ccff4d0de1fb1b7026c795c4): fix: [security] Pass community data API keys outside child https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch
- 2026-11-20 06:54 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133613",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:06:56.190222Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:07:18.747Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"launch.sh (community data launcher)",
"tests/testdata/init_community_data.py"
],
"product": "flowintel",
"programFiles": [
"launch.sh",
"tests/testdata/init_community_data.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\u0027s community data launcher script passes the admin API key as a command-line argument to a child Python helper process. On Unix-like systems, process arguments are readable by all local users via standard tools such as ps or by reading /proc/\u003cpid\u003e/cmdline, allowing any local user to observe the key while the helper process is running.\n\nAn attacker with local access to the host can capture the admin API key during the brief window in which the helper process is active. Possession of the key grants full administrative access to the Flowintel REST API, enabling unauthorized creation, modification, or deletion of threat intelligence data, users, roles, and organisations.\n\nPreconditions:\n- The victim must invoke the community data import or deletion command (launch.sh -tdc or -dtdc) with the API key supplied as a positional argument.\n- The attacker must have a local user account on the same host and be able to observe process listings during the helper execution window.\n\nImpact:\n- Disclosure of the Flowintel admin API key to any local user.\n- Subsequent full administrative control over the Flowintel instance via its REST API.\n\nAffected: \u003c4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-66",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-66 Exploiting Trusted Input in Untrusted Context"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "LOCAL",
"baseScore": 6.4,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "HIGH",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T06:54:46Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522 Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T07:38:24.421Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4"
}
],
"solutions": [
{
"lang": "en",
"value": "The launcher no longer forwards the admin API key in the child process command line. The key is now passed exclusively through the FLOWINTEL_ADMIN_API_KEY environment variable, which is not visible in process listings. A hidden terminal prompt (read -r -s) is provided for interactive use, and the Python helper reads the key from the environment by default. Legacy positional and --api-key argument forms remain functional for backward compatibility but emit a warning documenting the exposure risk."
}
],
"title": "Flowintel Community Data Launcher Exposes Admin API Key in Child Process Arguments",
"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 explicitly stated in the patch; all versions prior to commit 607e23000ea39172ccff4d0de1fb1b7026c795c4 are assumed affected.",
"The Flowintel REST API is assumed to be a separate component from the launcher script, justifying scope change (SC/SI/SA) in the CVSS vector.",
"The CAPEC-66 mapping is approximate; no CAPEC specifically covers local process-argument information disclosure, so the closest plausible pattern was selected.",
"PR:N assumes any unprivileged local user can read process arguments; on systems with restricted /proc access, PR may need to be raised.",
"The exposure window is limited to the duration of the helper process execution, but this is sufficient for a local attacker to capture the key."
],
"capecRationale": [
{
"capecId": "CAPEC-66",
"rationale": "The system places the API key in a context (process arguments) that is assumed to be private, but on multi-user Unix systems process arguments are visible to all local users. The attacker exploits this trust assumption by reading the key from the process table. This is the closest available CAPEC; no CAPEC specifically covers local process-argument sniffing, so CAPEC-66 is selected as the best approximation of exploiting a trusted-context assumption in an untrusted context."
}
],
"commit": "607e23000ea39172ccff4d0de1fb1b7026c795c4",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:L: The attacker must have local access to the host to read process arguments. AC:L: Reading process arguments via ps or /proc is trivial and requires no special conditions. AT:N: No data tampering is needed. PR:N: Any local user can read process arguments; no elevated privileges are required. UI:N: The attacker does not need victim interaction beyond the victim running the launcher. VC/VI/VA:N: The vulnerable component (launcher script) itself is not directly compromised. SC/SI/SA:H: The exposed admin API key grants full administrative access to the Flowintel REST API (a separate component), allowing complete read, write, and delete of all threat intelligence data, users, and configurations.",
"fixSummary": "The launcher no longer forwards the admin API key in the child process command line. The key is now passed exclusively through the FLOWINTEL_ADMIN_API_KEY environment variable, which is not visible in process listings. A hidden terminal prompt (read -r -s) is provided for interactive use, and the Python helper reads the key from the environment by default. Legacy positional and --api-key argument forms remain functional for backward compatibility but emit a warning documenting the exposure risk.",
"generatedAt": "2026-11-20T06:54:46.444981Z",
"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": "08c621737fc472a2a2ff140efe0acb92ce72c35429a443691b846d8182966fea",
"patchSummary": "launch.sh: Added a read_admin_api_key function that resolves the key from the FLOWINTEL_ADMIN_API_KEY environment variable, a hidden terminal prompt, or a legacy positional argument (with a warning). The test_data_community and delete_test_data_community functions now export the key as FLOWINTEL_ADMIN_API_KEY in the child environment instead of passing it as --api-key on the command line. init_community_data.py: Changed --api-key from required=True to default=os.environ.get(\u0027FLOWINTEL_ADMIN_API_KEY\u0027), added a parser.error() guard when no key is available, and updated docstrings. README.md and doc/user-manual.md: Updated usage examples to remove the positional key argument and document the environment-variable and hidden-prompt workflows.",
"patchTruncated": false,
"patches": [
{
"commit": "607e23000ea39172ccff4d0de1fb1b7026c795c4",
"date": "Fri, 6 Nov 2026 10:54:20 +0100",
"patchSha256": "08c621737fc472a2a2ff140efe0acb92ce72c35429a443691b846d8182966fea",
"retrievedAt": "2026-11-20T06:54:03.604758Z",
"source": "https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch",
"subject": "fix: [security] Pass community data API keys outside child"
}
],
"source": "https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T06:54:46Z",
"version": "2.0.3"
},
"subject": "fix: [security] Pass community data API keys outside child",
"weaknessRationale": [
{
"cweId": "CWE-200",
"rationale": "The admin API key is placed in process arguments (argv), which are readable by all local users via ps or /proc/\u003cpid\u003e/cmdline. This exposes a sensitive credential to unauthorized local actors."
},
{
"cweId": "CWE-522",
"rationale": "The credential (admin API key) is transmitted between the launcher and the helper process in a manner that does not protect it from local observation, failing to adequately safeguard the credential in transit."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (607e23000ea39172ccff4d0de1fb1b7026c795c4): fix: [security] Pass community data API keys outside child",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch"
],
"timestamp": "2026-11-06T09:54:20Z",
"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/607e23000ea39172ccff4d0de1fb1b7026c795c4.patch"
],
"timestamp": "2026-11-20T06:54:03.604758Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20041"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133613",
"datePublished": "2026-11-20T07:38:24.421Z",
"dateReserved": "2026-11-20T07:38:21.091Z",
"dateUpdated": "2026-11-20T18:07:18.747Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132664 (GCVE-0-2026-132664)
Vulnerability from cvelistv5 – Published: 2026-11-20 14:56 – Updated: 2026-11-20 16:30| Vendor | Product | Version | |
|---|---|---|---|
| EnterpriseDB | Postgres Enterprise Manager |
Affected:
2.0.1 , < 10.6.1
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132664",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T15:57:23.621844Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T16:30:59.688Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Postgres Enterprise Manager",
"vendor": "EnterpriseDB",
"versions": [
{
"lessThan": "10.6.1",
"status": "affected",
"version": "2.0.1",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "kta1kri"
}
],
"descriptions": [
{
"lang": "en",
"value": "In Postgres Enterprise Manager (PEM), any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted with a key that is the same in every PEM installation, so they can be decrypted.\nFrom PEM 10.6.1, PEM users can no longer read these passwords."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 7,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522 Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-321",
"description": "CWE-321 Use of Hard-coded Cryptographic Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T14:56:02.970Z",
"orgId": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
"shortName": "EDB"
},
"references": [
{
"url": "https://www.enterprisedb.com/docs/security/advisories/cve2026132664/"
}
],
"source": {
"discovery": "EXTERNAL"
}
}
},
"cveMetadata": {
"assignerOrgId": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
"assignerShortName": "EDB",
"cveId": "CVE-2026-132664",
"datePublished": "2026-11-20T14:56:02.970Z",
"dateReserved": "2026-11-18T22:27:58.954Z",
"dateUpdated": "2026-11-20T16:30:59.688Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131267 (GCVE-0-2026-131267)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:56 – Updated: 2026-11-19 19:56- CWE-522 - The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk SOAR |
Affected:
0 , < 8.8.0
(custom)
|
{
"containers": {
"cna": {
"affected": [
{
"product": "Splunk SOAR",
"vendor": "Splunk",
"versions": [
{
"lessThan": "8.8.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view and edit permissions could test a Lightweight Directory Access Protocol authentication provider and cause Splunk SOAR to send a stored directory service account bind password to a host that the user controls.\nThe vulnerability is possible because Splunk SOAR reuses a stored directory service provider credential when an authentication test uses a different directory service connection destination."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:56:24.423Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1108"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk SOAR to version 8.8.0 or higher."
}
],
"source": {
"advisory": "SVD-2026-1108",
"discovery": ""
},
"title": "Sensitive Information Disclosure through the REST API in Splunk SOAR"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131267",
"datePublished": "2026-11-19T19:56:24.423Z",
"dateReserved": "2026-11-17T20:26:14.308Z",
"dateUpdated": "2026-11-19T19:56:24.423Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131264 (GCVE-0-2026-131264)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:56 – Updated: 2026-11-19 20:37- CWE-522 - The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk SOAR |
Affected:
0 , < 8.8.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131264",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:26:12.163420Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:37:28.205Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Splunk SOAR",
"vendor": "Splunk",
"versions": [
{
"lessThan": "8.8.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send the stored root credential for an external credential store to a host that the user controls. Depending on the configuration, the exposed credential could include an access token, application secret, account password, or client certificate.\nThe vulnerability is possible because Splunk SOAR reuses the stored credential when the user changes the external credential store endpoint without supplying replacement credentials."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:56:22.725Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1108"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk SOAR to version 8.8.0 or higher."
}
],
"source": {
"advisory": "SVD-2026-1108",
"discovery": ""
},
"title": "Information Exposure through the REST API in Splunk SOAR"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131264",
"datePublished": "2026-11-19T19:56:22.725Z",
"dateReserved": "2026-11-17T20:26:14.308Z",
"dateUpdated": "2026-11-19T20:37:28.205Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130696 (GCVE-0-2026-130696)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:33 – Updated: 2026-11-18 19:17- CWE-522 - Insufficiently Protected Credentials
| URL | Tags |
|---|---|
| https://github.com/nocodb/nocodb/security/advisor… | vendor-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130696",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T19:16:49.061866Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T19:17:09.241Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "nocodb",
"vendor": "nocodb",
"versions": [
{
"lessThan": "2026.10.1",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2026.10.1",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2026.10.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "sfwani"
}
],
"datePublic": "2026-11-02T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "NocoDB before 2026.10.1 contains a credential exposure vulnerability in the connection-test endpoint that allows authorized integration users to redirect stored credentials by overriding connection host, port, and user fields. Attackers can point the test at a server they control to capture offline-crackable PostgreSQL md5 or MySQL handshakes and recover the stored database password."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:33:58.432Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-jcc2-3vff-7867)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-jcc2-3vff-7867"
}
],
"title": "NocoDB before 2026.10.1 Credential Exposure via Connection Test Endpoint",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-130696",
"datePublished": "2026-11-18T11:33:58.432Z",
"dateReserved": "2026-11-17T15:37:04.966Z",
"dateUpdated": "2026-11-18T19:17:09.241Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130627 (GCVE-0-2026-130627)
Vulnerability from cvelistv5 – Published: 2026-11-17 14:21 – Updated: 2026-11-17 18:04| Vendor | Product | Version | |
|---|---|---|---|
| a2a-java | a2a-java-sdk-http-client-vertx |
Affected:
1.3.2.Final , ≤ 1.4.0.Final
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130627",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T18:04:29.234797Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T18:04:59.755Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-w377-w7c6-c8hr"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "a2a-java-sdk-http-client-vertx",
"vendor": "a2a-java",
"versions": [
{
"lessThanOrEqual": "1.4.0.Final",
"status": "affected",
"version": "1.3.2.Final",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "manus-use"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard Authorization header (Bearer/Basic/OAuth) \u2014 plus every other header, including the allowlisted API-key headers \u2014 to the attacker-controlled authority. This breaks the project\u0027s own cross-transport invariant (SECURITY.md \u00a78, OkHttpPostRedirectHeaderLeakTest) that credentials are stripped on cross-authority redirects even when redirects are followed. The sibling JDK and OkHttp/Android transports strip Authorization; Vert.x uniquely does not. This is a \"fix introduced the bug\" variant \u2014 the follower was added by the GHSA-9rhm hardening PR (3ae82912, refined by a5e76a0b)."
}
],
"value": "The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard Authorization header (Bearer/Basic/OAuth) \u2014 plus every other header, including the allowlisted API-key headers \u2014 to the attacker-controlled authority. This breaks the project\u0027s own cross-transport invariant (SECURITY.md \u00a78, OkHttpPostRedirectHeaderLeakTest) that credentials are stripped on cross-authority redirects even when redirects are followed. The sibling JDK and OkHttp/Android transports strip Authorization; Vert.x uniquely does not. This is a \"fix introduced the bug\" variant \u2014 the follower was added by the GHSA-9rhm hardening PR (3ae82912, refined by a5e76a0b)."
}
],
"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"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T14:21:40.347Z",
"orgId": "74b3a70d-cca6-4d34-9789-e83b222ae3be",
"shortName": "redhat-cnalr"
},
"references": [
{
"url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-w377-w7c6-c8hr"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Upgrade to 1.5.0.Final or later. PR #1255 applies the shared RedirectHeaderPolicy to explicitly enabled, one-hop synchronous POST redirects across the JDK, Vert.x, and Android HTTP clients. The policy strips Authorization and the allowlisted API-key headers when a redirect crosses authorities. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue."
}
],
"value": "Upgrade to 1.5.0.Final or later. PR #1255 applies the shared RedirectHeaderPolicy to explicitly enabled, one-hop synchronous POST redirects across the JDK, Vert.x, and Android HTTP clients. The policy strips Authorization and the allowlisted API-key headers when a redirect crosses authorities. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Vert.x HTTP client forwards Authorization and all headers to cross-authority redirect target when followRedirects(true)",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "On affected versions, leave PostBuilder.followRedirects(false) (the default) so the SDK does not re-issue POST requests to redirect targets."
}
],
"value": "On affected versions, leave PostBuilder.followRedirects(false) (the default) so the SDK does not re-issue POST requests to redirect targets."
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "74b3a70d-cca6-4d34-9789-e83b222ae3be",
"assignerShortName": "redhat-cnalr",
"cveId": "CVE-2026-130627",
"datePublished": "2026-11-17T14:21:40.347Z",
"dateReserved": "2026-11-17T14:10:49.362Z",
"dateUpdated": "2026-11-17T18:04:59.755Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130626 (GCVE-0-2026-130626)
Vulnerability from cvelistv5 – Published: 2026-11-17 14:15 – Updated: 2026-11-17 18:05| Vendor | Product | Version | |
|---|---|---|---|
| a2a-java | a2a-java-sdk-http-client |
Affected:
1.3.0.Final , ≤ 1.4.0.Final
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130626",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T18:05:28.618775Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T18:05:55.445Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "a2a-java-sdk-http-client",
"vendor": "a2a-java",
"versions": [
{
"lessThanOrEqual": "1.4.0.Final",
"status": "affected",
"version": "1.3.0.Final",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "manus-use"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) \u2014 which is the SDK-documented way to enable POST redirects \u2014 silently follows cross-authority redirects on every credentialed GET/DELETE request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE."
}
],
"value": "The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) \u2014 which is the SDK-documented way to enable POST redirects \u2014 silently follows cross-authority redirects on every credentialed GET/DELETE request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE."
}
],
"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"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T14:15:56.700Z",
"orgId": "74b3a70d-cca6-4d34-9789-e83b222ae3be",
"shortName": "redhat-cnalr"
},
"references": [
{
"url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Upgrade to 1.5.0.Final or later. PR #1257 routes JDK GET, DELETE, and SSE requests through a client with native redirects disabled. Synchronous GET redirects are handled explicitly by the SDK using the shared RedirectHeaderPolicy; streaming requests do not follow redirects. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue."
}
],
"value": "Upgrade to 1.5.0.Final or later. PR #1257 routes JDK GET, DELETE, and SSE requests through a client with native redirects disabled. Synchronous GET redirects are handled explicitly by the SDK using the shared RedirectHeaderPolicy; streaming requests do not follow redirects. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "JDK HTTP client GET/DELETE follow cross-authority redirects with injected client, leaking API-key headers (POST-only gap)",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "On affected versions, supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following."
}
],
"value": "On affected versions, supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following."
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "74b3a70d-cca6-4d34-9789-e83b222ae3be",
"assignerShortName": "redhat-cnalr",
"cveId": "CVE-2026-130626",
"datePublished": "2026-11-17T14:15:56.700Z",
"dateReserved": "2026-11-17T14:10:49.361Z",
"dateUpdated": "2026-11-17T18:05:55.445Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-129494 (GCVE-0-2026-129494)
Vulnerability from cvelistv5 – Published: 2026-11-16 00:00 – Updated: 2026-11-18 14:05- CWE-522 - Insufficiently Protected Credentials
| URL | Tags |
|---|---|
| https://vul.yulun.ac.cn/20261115/cloudpaste/ | third-party-advisory |
| https://github.com/ling-drag0n/CloudPaste/issues/223 | issue-tracking |
| https://github.com/ling-drag0n/CloudPaste/blob/28… | technical-description |
| https://github.com/ling-drag0n/CloudPaste/blob/28… | technical-description |
| https://www.vulncheck.com/advisories/cloudpaste-1… | third-party-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| ling-drag0n | CloudPaste |
Affected:
1.1.0 , ≤ 1.9.1
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-129494",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T14:04:31.464939Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T14:05:00.786Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://vul.yulun.ac.cn/20261115/cloudpaste/"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:github/ling-drag0n/CloudPaste",
"product": "CloudPaste",
"repo": "https://github.com/ling-drag0n/CloudPaste",
"vendor": "ling-drag0n",
"versions": [
{
"lessThanOrEqual": "1.9.1",
"status": "affected",
"version": "1.1.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Wu Yulun"
}
],
"datePublic": "2026-11-15T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "CloudPaste 1.1.0 through 1.9.1 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain WebDAV storage credentials through the unauthenticated /api/proxy/link endpoint. Attackers who know a public share slug can retrieve the Basic Authorization header containing the WebDAV username and password, then read, modify, or delete files on the WebDAV server."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T00:00:36.989Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://vul.yulun.ac.cn/20261115/cloudpaste/"
},
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/ling-drag0n/CloudPaste/issues/223"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/ling-drag0n/CloudPaste/blob/282ea1c7fbbcd4fab40527664bf7479fd5bb922d/backend/src/routes/proxyLinkRoutes.js#L139-L167"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/ling-drag0n/CloudPaste/blob/282ea1c7fbbcd4fab40527664bf7479fd5bb922d/backend/src/storage/drivers/webdav/WebDavStorageDriver.js#L800-L819"
},
{
"name": "VulnCheck Advisory: CloudPaste 1.1.0 through 1.9.1 WebDAV Credential Disclosure via /api/proxy/link",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/cloudpaste-1.1.0-through-1.9.1-webdav-credential-disclosure-via-api-proxy-link"
}
],
"title": "CloudPaste 1.1.0 through 1.9.1 WebDAV Credential Disclosure via /api/proxy/link",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-129494",
"datePublished": "2026-11-16T00:00:36.989Z",
"dateReserved": "2026-11-15T16:14:12.267Z",
"dateUpdated": "2026-11-18T14:05:00.786Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Mitigation
Use an appropriate security mechanism to protect the credentials.
Mitigation
Make appropriate use of cryptography to protect the credentials.
Mitigation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
CAPEC-102: Session Sidejacking
Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
CAPEC-474: Signature Spoofing by Key Theft
An attacker obtains an authoritative or reputable signer's private signature key by theft and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.
CAPEC-50: Password Recovery Exploitation
An attacker may take advantage of the application feature to help users recover their forgotten passwords in order to gain access into the system with the same privileges as the original user. Generally password recovery schemes tend to be weak and insecure.
CAPEC-509: Kerberoasting
Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.
CAPEC-551: Modify Existing Service
When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
CAPEC-555: Remote Services with Stolen Credentials
This pattern of attack involves an adversary that uses stolen credentials to leverage remote services such as RDP, telnet, SSH, and VNC to log into a system. Once access is gained, any number of malicious activities could be performed.
CAPEC-560: Use of Known Domain Credentials
An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service.
CAPEC-561: Windows Admin Shares with Stolen Credentials
An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows administrator credentials (e.g. userID/password) to access Windows Admin Shares on a local machine or within a Windows domain.
CAPEC-600: Credential Stuffing
An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services.
CAPEC-644: Use of Captured Hashes (Pass The Hash)
An adversary obtains (i.e. steals or purchases) legitimate Windows domain credential hash values to access systems within the domain that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols.
CAPEC-645: Use of Captured Tickets (Pass The Ticket)
An adversary uses stolen Kerberos tickets to access systems/resources that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system/resource without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.
CAPEC-652: Use of Known Kerberos Credentials
An adversary obtains (i.e. steals or purchases) legitimate Kerberos credentials (e.g. Kerberos service account userID/password or Kerberos Tickets) with the goal of achieving authenticated access to additional systems, applications, or services within the domain.
CAPEC-653: Use of Known Operating System Credentials
An adversary guesses or obtains (i.e. steals or purchases) legitimate operating system credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the system, under the guise of an authenticated user or service. This applies to any Operating System.