CWE-116
Weakness Allowed-with-ReviewImproper Encoding or Escaping of Output
Abstraction: Class · Status: Draft
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
Dimensions
- Behavior-Type: Encoding or Escaping
- Behavior-Property: Improper
- Other: Output
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
Modes of introduction
Detection methods
Automated Static Analysis
This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.
Effectiveness: Moderate
This is not a perfect solution, since 100% accuracy and coverage are not feasible.
Automated Dynamic Analysis
This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
Notes
Maintenance · CWE 5.0 · 2026-10-28
The relationships between encoding/escaping as a protection mechanism (CWE-116) and its contribution to injection (CWE-74) needs to be better clarified in this entry and others.
Relationship
This weakness can be primary to all weaknesses related to injection (CWE-74) since the inherent nature of injection involves the violation of structured messages.
Relationship
CWE-116 and CWE-20 have a close association because, depending on the nature of the structured message, proper input validation can indirectly prevent special characters from changing the meaning of a structured message. For example, by validating that a numeric ID field should only contain the 0-9 characters, the programmer effectively prevents injection attacks.
However, input validation is not always sufficient, especially when less stringent data types must be supported, such as free-form text. Consider a SQL injection scenario in which a last name is inserted into a query. The name "O'Reilly" would likely pass the validation step since it is a common last name in the English language. However, it cannot be directly inserted into the database because it contains the "'" apostrophe character, which would need to be escaped or otherwise neutralized. In this case, stripping the apostrophe might reduce the risk of SQL injection, but it would produce incorrect behavior because the wrong name would be recorded.
Terminology
The usage of the "encoding" and "escaping" terms varies widely. For example, in some programming languages, the terms are used interchangeably, while other languages provide APIs that use both terms for different tasks. This overlapping usage extends to the Web, such as the "escape" JavaScript function whose purpose is stated to be encoding. The concepts of encoding and escaping predate the Web by decades. Given such a context, it is difficult for CWE to adopt a consistent vocabulary that will not be misinterpreted by some constituency.
Theoretical
This is a data/directive boundary error in which data boundaries are not sufficiently enforced before it is sent to a different control sphere.
Research Gap
While many published vulnerabilities are related to insufficient output encoding, there is such an emphasis on input validation as a protection mechanism that the underlying causes are rarely described. Within CVE, the focus is primarily on well-understood issues like cross-site scripting and SQL injection. It is likely that this weakness frequently occurs in custom protocols that support multiple encodings, which are not necessarily detectable with automated techniques.
Content history
Submitted by members of the CWE community to extend early CWE versions
added/updated demonstrative examples
updated Time_of_Introduction
updated Name, Relationships
updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships, Research_Gaps, Terminology_Notes, Theoretical_Notes
updated Description, Potential_Mitigations
updated Related_Attack_Patterns
updated Demonstrative_Examples
updated Relationships
updated Demonstrative_Examples, Potential_Mitigations
updated Detection_Factors, Potential_Mitigations, References, Taxonomy_Mappings
updated Potential_Mitigations
updated Potential_Mitigations
updated Relationship_Notes, Relationships
updated Common_Consequences, Relationships, Taxonomy_Mappings
updated Relationships, Taxonomy_Mappings
updated References, Relationships, Taxonomy_Mappings
updated Potential_Mitigations
updated References
updated Demonstrative_Examples, Relationships
updated Relationships
updated Relationships
updated Related_Attack_Patterns
updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Likelihood_of_Exploit, References, Taxonomy_Mappings
updated References
updated Relationships, Taxonomy_Mappings
updated Relationships
updated Relationships
updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations
updated Relationships, Terminology_Notes
updated Relationships
updated Observed_Examples
updated Description
updated References, Relationships, Time_of_Introduction
updated Mapping_Notes
updated Applicable_Platforms
updated References
updated Applicable_Platforms, Demonstrative_Examples, Relationships, Weakness_Ordinalities
updated Relationships
updated Applicable_Platforms, Background_Details, Common_Consequences, Description, Dimensions, References, Relationship_Notes, Relationships, Taxonomy_Mappings
906 vulnerabilities reference this CWE, most recent first.
CVE-2026-133178 (GCVE-0-2026-133178)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:11 – Updated: 2026-11-19 14:46| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/ade… | 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:21 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
5c27997cbe9f… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
adef89f5c827
|
fix: [security] Neutralise formulas in case and task CSV | 5c27997cbe9f… |
Fix summary
A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings—those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters—and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.
Patch summary
New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (=, +, -, @), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.
CVSS rationale
AV:N – exploitation occurs over the network via the web interface. AC:L – crafting formula-like text requires no special conditions. AT:N – no specific attack prerequisites. PR:L – the attacker needs editor-level access to create or modify case/task fields. UI:A – the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N – the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L – the secondary system (spreadsheet) may leak data via formula functions. SI:L – the secondary system's data integrity can be altered by injected formulas. SA:N – no availability impact on the secondary system.
Weakness rationale
- CWE-147 The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147.
- CWE-116 More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category.
Attack pattern rationale
- CAPEC-117 The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output.
Assumptions to verify
- The affected version range is not explicitly stated in the patch; the metadata field 'affected_version' contains the placeholder value '0'. All versions prior to commit adef89f5 are assumed affected.
- PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.
- The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim's spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.
- CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.
- The fullwidth Unicode formula triggers (=, +, -, @) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score.
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 |
8 | 11 | high | 5 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
- 2026-11-18 14:21 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133178",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:46:27.278959Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:46:40.447Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/tools/tools.py (_cases_to_csv)",
"app/utils/csv_utils.py (new)"
],
"product": "flowintel",
"programFiles": [
"app/tools/tools.py",
"app/utils/csv_utils.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 allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file.\n\nBecause no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text.\n\nThis can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration.\n\nThe vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.\n\nAffected: \u003c4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-117",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-117 CSV Injection"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "ACTIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/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": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:36Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-147",
"description": "CWE-147 Improper Neutralization of Input with Special Element Used for a Spreadsheet (CSV and DSL)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "CWE-116 Improper Encoding or Escaping of Output",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:11:56.276Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5"
}
],
"solutions": [
{
"lang": "en",
"value": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged."
}
],
"title": "CSV Formula Injection in Case and Task Exports in flowintel",
"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; the metadata field \u0027affected_version\u0027 contains the placeholder value \u00270\u0027. All versions prior to commit adef89f5 are assumed affected.",
"PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.",
"The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim\u0027s spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.",
"CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.",
"The fullwidth Unicode formula triggers (\uff1d, \uff0b, \uff0d, \uff20) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score."
],
"capecRationale": [
{
"capecId": "CAPEC-117",
"rationale": "The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output."
}
],
"commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N \u2013 exploitation occurs over the network via the web interface. AC:L \u2013 crafting formula-like text requires no special conditions. AT:N \u2013 no specific attack prerequisites. PR:L \u2013 the attacker needs editor-level access to create or modify case/task fields. UI:A \u2013 the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N \u2013 the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L \u2013 the secondary system (spreadsheet) may leak data via formula functions. SI:L \u2013 the secondary system\u0027s data integrity can be altered by injected formulas. SA:N \u2013 no availability impact on the secondary system.",
"fixSummary": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.",
"generatedAt": "2026-11-18T14:21:36.786654Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 8
}
],
"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": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
"patchSummary": "New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (\uff1d, \uff0b, \uff0d, \uff20), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.",
"patchTruncated": false,
"patches": [
{
"commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
"date": "Fri, 6 Nov 2026 10:54:23 +0100",
"patchSha256": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
"retrievedAt": "2026-11-18T14:21:08.763444Z",
"source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"subject": "fix: [security] Neutralise formulas in case and task CSV"
}
],
"source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:36Z",
"version": "2.0.3"
},
"subject": "fix: [security] Neutralise formulas in case and task CSV",
"weaknessRationale": [
{
"cweId": "CWE-147",
"rationale": "The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147."
},
{
"cweId": "CWE-116",
"rationale": "More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
],
"timestamp": "2026-11-06T09:54:23Z",
"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/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
],
"timestamp": "2026-11-18T14:21:08.763444Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20316"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133178",
"datePublished": "2026-11-19T14:11:56.276Z",
"dateReserved": "2026-11-19T14:11:54.087Z",
"dateUpdated": "2026-11-19T14:46:40.447Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131233 (GCVE-0-2026-131233)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:56 – Updated: 2026-11-20 19:23- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise Security |
Affected:
0 , < 8.7.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131233",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T19:23:21.948061Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T19:23:44.213Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Splunk Enterprise Security",
"vendor": "Splunk",
"versions": [
{
"lessThan": "8.7.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in endpoint summary data. If another user who can access the Time Center dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify some data available to the user who selects the row.\nThe vulnerability is possible because the Time Center dashboard does not safely escape endpoint summary values before inserting them into drilldown searches.\nFor more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Endpoint dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/endpoint-dashboards) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:56:04.995Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1106"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher."
}
],
"source": {
"advisory": "SVD-2026-1106",
"discovery": ""
},
"title": "SPL Injection through Time Center Dashboard Drilldowns in Splunk Enterprise Security",
"workarounds": [
{
"lang": "en",
"value": "The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround.\nSee [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131233",
"datePublished": "2026-11-19T19:56:04.995Z",
"dateReserved": "2026-11-17T20:26:14.305Z",
"dateUpdated": "2026-11-20T19:23:44.213Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131224 (GCVE-0-2026-131224)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-19 20:38- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk App for PCI Compliance |
Affected:
0 , < 8.7.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131224",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:26:29.592266Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:38:40.716Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Splunk App for PCI Compliance",
"vendor": "Splunk",
"versions": [
{
"lessThan": "8.7.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data that populates the Endpoint Changes report. Another user who holds the \"pci_analyst\" role could later click a corresponding table row. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify data available to that user.\nThe vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches.\nFor more information see Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 3.7,
"baseSeverity": "LOW",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:59.869Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1106"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher."
}
],
"source": {
"advisory": "SVD-2026-1106",
"discovery": ""
},
"title": "SPL Injection through the Endpoint Changes Report in Splunk Enterprise Security",
"workarounds": [
{
"lang": "en",
"value": "Turn off or remove the Splunk App for PCI Compliance.\nFor more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131224",
"datePublished": "2026-11-19T19:55:59.869Z",
"dateReserved": "2026-11-17T20:26:14.304Z",
"dateUpdated": "2026-11-19T20:38:40.716Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131213 (GCVE-0-2026-131213)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-21 04:55- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise Security |
Affected:
0 , < 8.7.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131213",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T00:00:00+00:00",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T04:55:32.832Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Splunk Enterprise Security",
"vendor": "Splunk",
"versions": [
{
"lessThan": "8.7.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise Security versions below 8.7.0, a user who holds the \"ess_analyst\" Splunk Enterprise Security role could store attacker-controlled data in finding exclusion rule metadata. Another authenticated user could later open the Finding Exclusion Rules page. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opened the page. The first user could access data and perform actions available to the later user.\nThe vulnerability is possible because Splunk Enterprise Security does not escape backslashes in finding exclusion rule metadata before adding the values to a page search.\nFor more information see Finding exclusions in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/user-and-entity-behavior-analytics/finding-exclusions-in-splunk-enterprise-security) and Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 6.7,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:53.758Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1106"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher."
}
],
"source": {
"advisory": "SVD-2026-1106",
"discovery": ""
},
"title": "SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131213",
"datePublished": "2026-11-19T19:55:53.758Z",
"dateReserved": "2026-11-17T20:26:14.303Z",
"dateUpdated": "2026-11-21T04:55:32.832Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131183 (GCVE-0-2026-131183)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-20 04:57- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise |
Affected:
10.4 , < 10.4.5
(custom)
Affected: 10.2 , < 10.2.9 (custom) Affected: 10.0 , < 10.0.12 (custom) Affected: 9.4 , < 9.4.17 (custom) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131183",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T00:00:00+00:00",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T04:57:13.519Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"modules": [
"Splunk Web"
],
"product": "Splunk Enterprise",
"vendor": "Splunk",
"versions": [
{
"lessThan": "10.4.5",
"status": "affected",
"version": "10.4",
"versionType": "custom"
},
{
"lessThan": "10.2.9",
"status": "affected",
"version": "10.2",
"versionType": "custom"
},
{
"lessThan": "10.0.12",
"status": "affected",
"version": "10.0",
"versionType": "custom"
},
{
"lessThan": "9.4.17",
"status": "affected",
"version": "9.4",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the \"power\" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another user opens the affected dashboard in Splunk Web, those injected commands execute with the viewing user\u0027s permissions, potentially allowing the low-privileged user to access stored credentials and write data to indexes.\nThe vulnerability is possible because Splunk Enterprise does not correctly escape user-supplied content when it rewrites a search, which lets the rewritten search include additional SPL commands.\nThe vulnerability requires another user to open the dashboard in Splunk Web. Consequently, a user who holds the \"power\" Splunk role should not be able to exploit the vulnerability at will.\nFor more information see SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:34.170Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1103"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher."
}
],
"source": {
"advisory": "SVD-2026-1103",
"discovery": ""
},
"title": "SPL Injection through Classic Dashboard in Splunk Enterprise"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131183",
"datePublished": "2026-11-19T19:55:34.170Z",
"dateReserved": "2026-11-17T20:26:14.300Z",
"dateUpdated": "2026-11-20T04:57:13.519Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131182 (GCVE-0-2026-131182)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-20 14:02- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise |
Affected:
10.4 , < 10.4.5
(custom)
Affected: 10.2 , < 10.2.9 (custom) Affected: 10.0 , < 10.0.12 (custom) Affected: 9.4 , < 9.4.17 (custom) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131182",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T04:57:13.191294Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T14:02:22.279Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"modules": [
"splunkd"
],
"product": "Splunk Enterprise",
"vendor": "Splunk",
"versions": [
{
"lessThan": "10.4.5",
"status": "affected",
"version": "10.4",
"versionType": "custom"
},
{
"lessThan": "10.2.9",
"status": "affected",
"version": "10.2",
"versionType": "custom"
},
{
"lessThan": "10.0.12",
"status": "affected",
"version": "10.0",
"versionType": "custom"
},
{
"lessThan": "9.4.17",
"status": "affected",
"version": "9.4",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the \"power\" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability.\nThe vulnerability is possible because Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search.\nThe vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker, a user who holds the \"power\" Splunk role, should not be able to exploit the vulnerability at will."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.6,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:33.614Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1103"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher."
}
],
"source": {
"advisory": "SVD-2026-1103",
"discovery": ""
},
"title": "SPL Injection through Shared Dashboards in Splunk Enterprise"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131182",
"datePublished": "2026-11-19T19:55:33.614Z",
"dateReserved": "2026-11-17T20:26:14.300Z",
"dateUpdated": "2026-11-20T14:02:22.279Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131180 (GCVE-0-2026-131180)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-20 16:52- CWE-116 - The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise |
Affected:
10.4 , < 10.4.5
(custom)
Affected: 10.2 , < 10.2.9 (custom) Affected: 10.0 , < 10.0.12 (custom) Affected: 9.4 , < 9.4.17 (custom) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131180",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T16:52:40.646810Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T16:52:51.594Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"modules": [
"Splunk Web"
],
"product": "Splunk Enterprise",
"vendor": "Splunk",
"versions": [
{
"lessThan": "10.4.5",
"status": "affected",
"version": "10.4",
"versionType": "custom"
},
{
"lessThan": "10.2.9",
"status": "affected",
"version": "10.2",
"versionType": "custom"
},
{
"lessThan": "10.0.12",
"status": "affected",
"version": "10.0",
"versionType": "custom"
},
{
"lessThan": "9.4.17",
"status": "affected",
"version": "9.4",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the \"power\" Splunk role could create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With this access, the user who created the dashboard could expose stored credentials and write data to an index.\nThe vulnerability is possible because Splunk Enterprise does not correctly escape field names in searches that use the rename command.\nFor more information see rename (https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.4/search-commands/rename) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:32.516Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1103"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher."
}
],
"source": {
"advisory": "SVD-2026-1103",
"discovery": ""
},
"title": "SPL Injection through the rename Command in Splunk Enterprise"
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131180",
"datePublished": "2026-11-19T19:55:32.516Z",
"dateReserved": "2026-11-17T20:26:14.300Z",
"dateUpdated": "2026-11-20T16:52:51.594Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130687 (GCVE-0-2026-130687)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:33 – Updated: 2026-11-21 03:00- CWE-116 - Improper Encoding or Escaping of Output
| URL | Tags |
|---|---|
| https://github.com/nocodb/nocodb/security/advisor… | vendor-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130687",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-21T02:59:42.459821Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T03:00:19.107Z",
"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": "manus-pi"
},
{
"lang": "en",
"type": "reporter",
"value": "manus-use"
}
],
"datePublic": "2026-11-02T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "NocoDB before 2026.10.1 contains a stored CSS injection vulnerability that allows authenticated Commenter or Editor users to inject inline styles by placing single quotes in mention text. Attackers can break out of the single-quoted data-id attribute in comments or rich text cells to overlay or rearrange the interface for other viewers."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.1,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "LOW",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 4.6,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "Improper Encoding or Escaping of Output",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:33:57.555Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-qgv3-m9j5-jph8)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-qgv3-m9j5-jph8"
}
],
"title": "NocoDB before 2026.10.1 Stored CSS Injection via Unescaped Mention Attribute",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-130687",
"datePublished": "2026-11-18T11:33:57.555Z",
"dateReserved": "2026-11-17T15:36:15.272Z",
"dateUpdated": "2026-11-21T03:00:19.107Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-129100 (GCVE-0-2026-129100)
Vulnerability from cvelistv5 – Published: 2026-11-13 15:38 – Updated: 2026-11-18 14:54- CWE-116 - Improper Encoding or Escaping of Output
| URL | Tags |
|---|---|
| https://www.cudy.com/pages/security-advisory/cudy… | vendor-advisory |
| https://www.cudy.com/en-us/pages/download-center/… | release-notes |
| https://d1jvyy13vm72kv.cloudfront.net/device/upgr… | patch |
| https://www.vulncheck.com/advisories/cudy-tr3000-… | third-party-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| Shenzhen Cudy Technology Co., Ltd. | TR3000 1.0 |
Affected:
0 , < 2.5.42
(semver)
Unaffected: 2.5.42 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-129100",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T14:54:02.957793Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T14:54:11.942Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "TR3000 1.0",
"vendor": "Shenzhen Cudy Technology Co., Ltd.",
"versions": [
{
"lessThan": "2.5.42",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.5.42",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Jincheng Wang (@winmt) from Nanjing University of Posts and Telecommunications"
},
{
"lang": "en",
"type": "finder",
"value": "Xiaolei Liu from National Interdisciplinary Research Center of Engineering Physics"
},
{
"lang": "en",
"type": "finder",
"value": "Kangyi Ding from National Interdisciplinary Research Center of Engineering Physics"
}
],
"datePublic": "2026-11-13T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Cudy TR3000 before 2.5.42 contains a remote code execution vulnerability that allows authenticated administrators to execute commands as root by uploading crafted OpenVPN private or tls-auth keys. Attackers can close the inline key block with \u003c/key\u003e, inject directives such as tls-verify that bypass the .ovpn denylist, and have OpenVPN execute the hook as root."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"privilegesRequired": "HIGH",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "Improper Encoding or Escaping of Output",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T15:07:12.764Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "Cudy Security Advisory Cudy-SA-26-11-VTKROF",
"tags": [
"vendor-advisory"
],
"url": "https://www.cudy.com/pages/security-advisory/cudy-sa-26-11-vtkrof"
},
{
"name": "Cudy TR3000 1.0 Download Center",
"tags": [
"release-notes"
],
"url": "https://www.cudy.com/en-us/pages/download-center/tr3000-1-0"
},
{
"name": "Cudy TR3000 Firmware 2.5.42",
"tags": [
"patch"
],
"url": "https://d1jvyy13vm72kv.cloudfront.net/device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip"
},
{
"name": "VulnCheck Advisory: Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Key Upload Injection",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection"
}
],
"title": "Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Key Upload Injection",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-129100",
"datePublished": "2026-11-13T15:38:31.536Z",
"dateReserved": "2026-11-13T15:31:00.206Z",
"dateUpdated": "2026-11-18T14:54:11.942Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-128348 (GCVE-0-2026-128348)
Vulnerability from cvelistv5 – Published: 2026-11-13 09:33 – Updated: 2026-11-13 17:51- CWE-116 - Improper Encoding or Escaping of Output
| URL | Tags |
|---|---|
| https://github.com/exceljs/exceljs | product |
| https://github.com/mateocallec/exceljs-hardened/s… | third-party-advisory |
| https://github.com/exceljs/exceljs/blob/v4.4.0/li… | technical-description |
| https://www.vulncheck.com/advisories/exceljs-thro… | third-party-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-128348",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-13T17:50:31.305356Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-13T17:51:06.150Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:npm/exceljs",
"product": "exceljs",
"vendor": "exceljs",
"versions": [
{
"lessThanOrEqual": "4.4.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:exceljs_project:exceljs:*:*:*:*:*:*:*:*",
"versionEndIncluding": "4.4.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Mat\u00e9o Florian Callec"
}
],
"datePublic": "2026-10-16T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "ExcelJS through 4.4.0 contains a formula injection vulnerability in the totals row formula getter in lib/doc/table.js that fails to escape [, ], # and \u0027 characters in structured reference column names. Attackers can supply column names containing ] via untrusted input like imported CSV headers to inject formulas such as HYPERLINK that exfiltrate cell values when users open and click the generated workbook."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/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.2,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "Improper Encoding or Escaping of Output",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-13T09:33:30.358Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"product"
],
"url": "https://github.com/exceljs/exceljs"
},
{
"name": "GitHub Security Advisory (GHSA-qjfh-3mh9-356v)",
"tags": [
"third-party-advisory"
],
"url": "https://github.com/mateocallec/exceljs-hardened/security/advisories/GHSA-qjfh-3mh9-356v"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/exceljs/exceljs/blob/v4.4.0/lib/doc/table.js#L84-L104"
},
{
"name": "VulnCheck Advisory: ExcelJS through 4.4.0 Formula Injection via Table Totals Row Column Names",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/exceljs-through-4.4.0-formula-injection-via-table-totals-row-column-names"
}
],
"title": "ExcelJS through 4.4.0 Formula Injection via Table Totals Row Column Names",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-128348",
"datePublished": "2026-11-13T09:33:30.358Z",
"dateReserved": "2026-11-13T01:20:43.948Z",
"dateUpdated": "2026-11-13T17:51:06.150Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Mitigation MIT-4.3
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.
- Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
Mitigation MIT-27
Strategy: Parameterization
- If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
- For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
Mitigation
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
Mitigation
In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.
Mitigation
Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
Mitigation
Fully specify which encodings are required by components that will be communicating with each other.
Mitigation
When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
CAPEC-104: Cross Zone Scripting
An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security.
CAPEC-73: User-Controlled Filename
An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
CAPEC-81: Web Server Logs Tampering
Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
CAPEC-85: AJAX Footprinting
This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.