deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-74rh-c5rh-88vg
Package: org.xwiki.platform:xwiki-platform-web (MAVEN)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-1021: Improper Restriction of Rendered UI Layers or Frames
Vulnerable versions: >= 17.0.0-rc-1, < 17.4.6
Patched in: 17.4.6

Summary: XWiki vulnerable to click-jacking through CSS injection in comments

Details:
### Impact

It's possible using comments to inject CSS that would transform the full wiki in a link area leading to a malicious page. All versions of XWiki are impacted by this kind of attack. 

### Patches

The problem has been patched not by preventing injecting CSS in comments, which is currently a feature of XWiki, but by requiring confirmation from users when driving them to untrusted domains after clicking on a link, thus preventing any click-jacking attack. 
This security measure has been put in place in XWiki 17.9.0, 17.4.6, 16.10.13.

### Workarounds

There's no out-of-the-box workaround, but it should be possible to partly reuse [the javascript code provided for the security measure](https://github.com/xwiki/xwiki-platform/blob/xwiki-platform-17.9.0/xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/src/main/webapp/resources/uicomponents/link/link-protection.js) in a JSX object inside the wiki, to request the same kind of confirmation. 

### References
  * JIRA ticket: https://jira.xwiki.org/browse/XWIKI-23433
  * Documentation of the new security measure: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/17.9.0RC1/Entry006/
  * Commit for the security fix: https://github.com/xwiki/xwiki-platform/commit/29cb81f3a5387cf822d7e7534bdd63903275f86b

### For more information

If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki.org](https://jira.xwiki.org/)
* Email us at [Security Mailing List](mailto:security@xwiki.org)

### Attribution

Thanks Tomas Keech (Sentrium Security Ltd) for reporting this vulnerability.
GitHub Security Advisory: GHSA-74rh-c5rh-88vg
Package: org.xwiki.platform:xwiki-platform-web (MAVEN)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-1021: Improper Restriction of Rendered UI Layers or Frames
Vulnerable versions: >= 17.5.0, < 17.9.0
Patched in: 17.9.0

Summary: XWiki vulnerable to click-jacking through CSS injection in comments

Details:
### Impact

It's possible using comments to inject CSS that would transform the full wiki in a link area leading to a malicious page. All versions of XWiki are impacted by this kind of attack. 

### Patches

The problem has been patched not by preventing injecting CSS in comments, which is currently a feature of XWiki, but by requiring confirmation from users when driving them to untrusted domains after clicking on a link, thus preventing any click-jacking attack. 
This security measure has been put in place in XWiki 17.9.0, 17.4.6, 16.10.13.

### Workarounds

There's no out-of-the-box workaround, but it should be possible to partly reuse [the javascript code provided for the security measure](https://github.com/xwiki/xwiki-platform/blob/xwiki-platform-17.9.0/xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/src/main/webapp/resources/uicomponents/link/link-protection.js) in a JSX object inside the wiki, to request the same kind of confirmation. 

### References
  * JIRA ticket: https://jira.xwiki.org/browse/XWIKI-23433
  * Documentation of the new security measure: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/17.9.0RC1/Entry006/
  * Commit for the security fix: https://github.com/xwiki/xwiki-platform/commit/29cb81f3a5387cf822d7e7534bdd63903275f86b

### For more information

If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki.org](https://jira.xwiki.org/)
* Email us at [Security Mailing List](mailto:security@xwiki.org)

### Attribution

Thanks Tomas Keech (Sentrium Security Ltd) for reporting this vulnerability.
GitHub Security Advisory: GHSA-c244-p6m5-vqj6
Package: org.apache.shiro:shiro-spring (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-289: Authentication Bypass by Alternate Name
Vulnerable versions: <= 2.0.6
Patched in: 2.1.0

Summary: Apache Shiro has an Authentication Bypass

Details:
### Impact

**Authentication Bypass:**
A vulnerability exists in Apache Shiro that allows authentication bypass for static files when served from a case-insensitive filesystem (such as the default configuration on macOS or Windows).

The issue arises when Shiro's URL filters are configured with lower-case rules (a common default), but the underlying operating system treats mixed-case filenames as identical. An attacker can access protected static resources by varying the capitalization of the filename in the request (e.g., requesting `/SECRET.TXT` to bypass a rule for `/secret.txt`).

This issue specifically affects static file handling and does not impact dynamic resource paths that are case-sensitive.

### Patches
Users should upgrade to Apache Shiro **2.1.0** or later.

**Important Configuration Note:**
Version 2.1.0 introduces a new configuration parameter to handle case-insensitivity, which must be enabled manually to resolve the issue:

* **shiro.ini:**
    ```ini
    filterChainResolver.caseInsensitive = true
    ```
* **Spring Boot (application.properties):**
    ```properties
    shiro.caseInsensitive=true
    ```

*Note: Apache Shiro 3.0.0 (upcoming) will enable this setting by default.*

### Workarounds
* Ensure that the filesystem hosting the application is case-sensitive (e.g., Linux/Unix).
* Manually configure all Shiro filter chains to handle all possible case variations of protected filenames (not recommended due to complexity).

### Resources
* [CVE-2026-23903](https://nvd.nist.gov/vuln/detail/CVE-2026-23903)
* [Mailing List Announcement](https://lists.apache.org/thread/5jjf0hnjcol58z2m5y255c7scz1lnp8k)
* [OSS-Security List](http://www.openwall.com/lists/oss-security/2026/02/08/1)
GitHub Security Advisory: GHSA-pqqf-7hxm-rj5r
Package: org.open-metadata:openmetadata-sdk (MAVEN)
Severity: HIGH (CVSS 7.6)
CWE: CWE-269: Improper Privilege Management
Vulnerable versions: < 1.11.8
Patched in: 1.11.8

Summary: Leaky JWTs in OpenMetadata exposing highly-privileged bot users

Details:
### Summary
Calls issued by the UI against `/api/v1/ingestionPipelines` leak JWTs used by `ingestion-bot` for certain services (Glue / Redshift / Postgres)

### Details
Any read-only user can gain access to a highly privileged account, typically which has the Ingestion Bot Role. This enables destructive changes in OpenMetadata instances, and potential data leakage (e.g. sample data, or service metadata which would be unavailable per roles/policies). 


### PoC
I was able to extract the JWT used by the bot/agent populating [sample_athena.default](https://sandbox.open-metadata.org/database/sample_athena.default) in the Collate Sandbox. To prove this out, I mutated the description to this UUID: `fe2e4cc1-da72-4acf-8535-112a3cfa9c7e,` which you can see  @ https://sandbox.open-metadata.org/database/sample_athena.default.

#### Steps to Reproduce

* Create a Collate Sandbox account; these are non-admin accounts by default with minimal permissions.
* Open the Developer Console
* Go to the Services Page. In this case, [sample_athena](https://sandbox.open-metadata.org/service/databaseServices/sample_athena?showDeletedTables=false&currentPage=1), though other services 
* In the Network tab, introspect the request made to api/v1/services/ingestionPipelines, and find the jwtToken in the response:
<img width="1329" height="299" alt="image" src="https://github.com/user-attachments/assets/0c405776-159e-4188-9591-ed8cc71bc596" />

* Use the JWT to issue (potentially destructive) API calls
<img width="3024" height="1798" alt="image" src="https://github.com/user-attachments/assets/ab40b528-4d2b-404b-8f8a-482a1693e179" />

* Resulting mutated description:
<img width="622" height="399" alt="image" src="https://github.com/user-attachments/assets/3fa630ff-93b5-4b7d-8e3c-220f8a84a23a" />

Note that this is also the case for these services, among others:
* [acme_nexus_redshift](https://sandbox.open-metadata.org/service/databaseServices/acme_nexus_redshift) 
* [sample_postgres](https://sandbox.open-metadata.org/service/databaseServices/sample_postgres)

### Proposed Remediation
Redact jwtToken in API payload.
Implement role-based filtering - Only return JWT tokens to users with explicit admin/service account permissions
(for Admins) Rotate Ingestion Bot Tokens in affected environments

### Impact
_What kind of vulnerability is it? Who is impacted?_

* Vulnerability Type: Privilege Escalation
* Risk: User impersonation, even for those with read-only access, can lead to destructive outcomes if malicious actors leverage the leaked JWT.
GitHub Security Advisory: GHSA-fpq4-r87v-g246
Package: org.thingsboard:application (MAVEN)
Severity: MODERATE (CVSS 5.4)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 4.2.1
Patched in: 4.2.1

Summary: ThingsBoard vulnerable to stored cross-site scripting (XSS) vulnerability in the dashboard's Image Upload Gallery feature

Details:
ThingsBoard versions < 4.2.1 contain a stored cross-site scripting (XSS) vulnerability in the dashboard's Image Upload Gallery feature. An attacker can upload an SVG file containing malicious JavaScript, which may be executed when the file is rendered in the UI. This issue results from insufficient sanitization and improper content-type validation of uploaded SVG files.
GitHub Security Advisory: GHSA-q672-hfc7-g833
Package: org.apache.druid.extensions:druid-basic-security (MAVEN)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 0.17.0, < 36.0.0
Patched in: 36.0.0

Summary: Apache Druid Vulnerable to Authentication Bypass

Details:
Affected Products and Versions
  *  Apache Druid
  *  Affected Versions: 0.17.0 through 35.x (all versions prior to 36.0.0)
  *  Prerequisites:  *  druid-basic-security extension enabled
  *  LDAP authenticator configured
  *  Underlying LDAP server permits anonymous bind                                                                                                                                                   






Vulnerability Description

An authentication bypass vulnerability exists in Apache Druid when using the druid-basic-security extension with LDAP authentication. If the underlying LDAP server is configured to allow anonymous
binds, an attacker can bypass authentication by providing an existing username with an empty password. This allows unauthorized access to otherwise restricted Druid resources without valid credentials.

The vulnerability stems from improper validation of LDAP authentication responses when anonymous binds are permitted, effectively treating anonymous bind success as valid user authentication. 

Impact

A remote, unauthenticated attacker can:
  *  Gain unauthorized access to the Apache Druid cluster
  *  Access sensitive data stored in Druid datasources
  *  Execute queries and potentially manipulate data
  *  Access administrative interfaces if the bypassed account has elevated privileges
  *  Completely compromise the confidentiality, integrity, and availability of the Druid deployment                                                                                                                                                                                    


Mitigation
 
Immediate Mitigation (No Druid Upgrade Required):                                                                                                                                                    
  *  Disable anonymous bind on your LDAP server. This prevents the vulnerability from being exploitable and is the recommended immediate action.



Resolution
  *  Upgrade Apache Druid to version 36.0.0 or later, which includes fixes to properly reject anonymous LDAP bind attempts.
GitHub Security Advisory: GHSA-c4qc-4q9p-m9q9
Package: org.apache.shiro:shiro-core (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-208: Observable Timing Discrepancy
Vulnerable versions: < 2.1.0
Patched in: 2.1.0

Summary: Apache Shiro Affected by an Observable Timing Discrepancy Vulnerability

Details:
Observable Timing Discrepancy vulnerability in Apache Shiro.

This issue affects Apache Shiro: from 1.*, 2.* before 2.0.7.

Users are recommended to upgrade to version 2.0.7 or later, which fixes the issue.

Prior to Shiro 2.0.7, code paths for non-existent vs. existing users are different enough,
that a brute-force attack may be able to tell, by timing the requests only, determine if
the request failed because of a non-existent user vs. wrong password.

The most likely attack vector is a local attack only.
Shiro security model  https://shiro.apache.org/security-model.html#username_enumeration  discusses this as well.

Typically, brute force attack can be mitigated at the infrastructure level.
GitHub Security Advisory: GHSA-xr72-g735-4vwp
Package: org.neo4j:neo4j (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-117: Improper Output Neutralization for Logs
Vulnerable versions: < 2026.01
Patched in: 2026.01

Summary: Neo4j Enterprise and Community editions have insufficient escaping of unicode characters in query log

Details:
Insufficient escaping of unicode characters in query log in Neo4j Enterprise and Community editions prior to 2026.01 can lead to XSS if the user opens the logs in a tool that treats them as HTML. There is no security impact on Neo4j products, but this advisory is released as a precaution to treat the logs as plain text if using versions prior to 2026.01.

Proof of concept exploit:  https://github.com/JoakimBulow/CVE-2026-1337
GitHub Security Advisory: GHSA-j382-5jj3-vw4j
Package: io.undertow:undertow-core (MAVEN)
Severity: CRITICAL (CVSS 9.6)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 2.2.39.Final
Patched in: 2.2.39.Final

Summary: Undertow HTTP server core doesn't properly validate the Host header in incoming HTTP requests

Details:
A flaw was found in the Undertow HTTP server core, which is used in WildFly, JBoss EAP, and other Java applications. The Undertow library fails to properly validate the Host header in incoming HTTP requests. As a result, requests containing malformed or malicious Host headers are processed without rejection, enabling attackers to poison caches, perform internal network scans, or hijack user sessions.
GitHub Security Advisory: GHSA-j382-5jj3-vw4j
Package: io.undertow:undertow-core (MAVEN)
Severity: CRITICAL (CVSS 9.6)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 2.3.0.Alpha1, < 2.3.21.Final
Patched in: 2.3.21.Final

Summary: Undertow HTTP server core doesn't properly validate the Host header in incoming HTTP requests

Details:
A flaw was found in the Undertow HTTP server core, which is used in WildFly, JBoss EAP, and other Java applications. The Undertow library fails to properly validate the Host header in incoming HTTP requests. As a result, requests containing malformed or malicious Host headers are processed without rejection, enabling attackers to poison caches, perform internal network scans, or hijack user sessions.
GitHub Security Advisory: GHSA-4j3g-rwwq-4p54
Package: org.neo4j:neo4j (MAVEN)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-532: Insertion of Sensitive Information into Log File
Vulnerable versions: >= 2025.01.0, < 2026.01.3
Patched in: 2026.01.3

Summary: Neo4j Enterprise and Community vulnerable to a potential information disclosure

Details:
Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.

The "obfuscate_literals" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.

Neo4j recommends upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If a project's configuration had db.logs.query.obfuscate_literals enabled, and users wish for the obfuscation to cover the error messages as well, theyneed to enable the new configuration setting db.logs.query.obfuscate_errors once they have upgraded Neo4j.
GitHub Security Advisory: GHSA-4j3g-rwwq-4p54
Package: org.neo4j:neo4j (MAVEN)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-532: Insertion of Sensitive Information into Log File
Vulnerable versions: < 5.26.21
Patched in: 5.26.21

Summary: Neo4j Enterprise and Community vulnerable to a potential information disclosure

Details:
Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.

The "obfuscate_literals" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.

Neo4j recommends upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If a project's configuration had db.logs.query.obfuscate_literals enabled, and users wish for the obfuscation to cover the error messages as well, theyneed to enable the new configuration setting db.logs.query.obfuscate_errors once they have upgraded Neo4j.
GitHub Security Advisory: GHSA-v84m-gfw5-hm2w
Package: org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui (MAVEN)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 4.0.0, < 4.0.4
Patched in: 4.0.4

Summary: Apache Syncope: Reflected XSS on Enduser Login

Details:
Reflected XSS in Apache Syncope's Enduser Login page.

An attacker that tricks a legitimate user into clicking a malicious link and logging in to Syncope Enduser could steal that user's credentials.

This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.

Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
GitHub Security Advisory: GHSA-v84m-gfw5-hm2w
Package: org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui (MAVEN)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 3.0.0, < 3.0.16
Patched in: 3.0.16

Summary: Apache Syncope: Reflected XSS on Enduser Login

Details:
Reflected XSS in Apache Syncope's Enduser Login page.

An attacker that tricks a legitimate user into clicking a malicious link and logging in to Syncope Enduser could steal that user's credentials.

This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.

Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
GitHub Security Advisory: GHSA-73f3-rqqf-2j54
Package: org.apache.syncope.client.idrepo:syncope-client-idrepo-console (MAVEN)
Severity: MODERATE (CVSS 4.9)
CWE: CWE-611: Improper Restriction of XML External Entity Reference
Vulnerable versions: >= 4.0.0, < 4.0.4
Patched in: 4.0.4

Summary: Apache Syncope: Console XXE on Keymaster parameters

Details:
Improper Restriction of XML External Entity Reference vulnerability in Apache Syncope Console. An administrator with adequate entitlements to create or edit Keymaster parameters via Console can construct malicious XML text to launch an XXE attack, thereby causing sensitive data leakage occurs.

This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.

Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
GitHub Security Advisory: GHSA-73f3-rqqf-2j54
Package: org.apache.syncope.client.idrepo:syncope-client-idrepo-console (MAVEN)
Severity: MODERATE (CVSS 4.9)
CWE: CWE-611: Improper Restriction of XML External Entity Reference
Vulnerable versions: >= 3.0.0, < 3.0.16
Patched in: 3.0.16

Summary: Apache Syncope: Console XXE on Keymaster parameters

Details:
Improper Restriction of XML External Entity Reference vulnerability in Apache Syncope Console. An administrator with adequate entitlements to create or edit Keymaster parameters via Console can construct malicious XML text to launch an XXE attack, thereby causing sensitive data leakage occurs.

This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.

Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
GitHub Security Advisory: GHSA-gj28-gw7w-3pxc
Package: org.craftercms:craftercms (MAVEN)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-913: Improper Control of Dynamically-Managed Code Resources
Vulnerable versions: >= 4.0.0, < 4.5.0
Patched in: 4.5.0

Summary: Crafter CMS has Improper Control of Dynamically-Managed Code Resources

Details:
Improper Control of Dynamically-Managed Code Resources vulnerability in Crafter Studio of Crafter CMS allows authenticated developers to execute OS commands via Groovy Sandbox Bypass. By inserting malicious Groovy elements, an attacker may bypass sandbox restrictions and obtain RCE (Remote Code Execution).
GitHub Security Advisory: GHSA-wj3h-wx8g-x699
Package: ai.h2o:h2o-core (MAVEN)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-73: External Control of File Name or Path
Vulnerable versions: <= 3.46.0.1
Patched in: unpatched

Summary: H2O has an External Control of File Name or Path vulnerability

Details:
A vulnerability in h2oai/h2o-3 version 3.46.0.1 allows remote attackers to write arbitrary data to any file on the server. This is achieved by exploiting the `/3/Parse` endpoint to inject attacker-controlled data as the header of an empty file, which is then exported using the `/3/Frames/framename/export` endpoint. The impact of this vulnerability includes the potential for remote code execution and complete access to the system running h2o-3, as attackers can overwrite critical files such as private SSH keys or script files.
GitHub Security Advisory: GHSA-fwhw-chw4-gh37
Package: org.keycloak:keycloak-parent (MAVEN)
Severity: LOW (CVSS 2.7)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: <= 26.5.2
Patched in: unpatched

Summary: Keycloak Server-Side Request Forgery (SSRF) vulnerability

Details:
A flaw was found in Keycloak’s CIBA feature where insufficient validation of client-configured backchannel notification endpoints could allow blind server-side requests to internal services.
GitHub Security Advisory: GHSA-qmgx-j96g-4428
Package: org.apache.cxf:cxf-rt-databinding-aegis (MAVEN)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: >= 4.0.0, < 4.0.4
Patched in: 4.0.4

Summary: SSRF vulnerability using the Aegis DataBinding in Apache CXF

Details:
A SSRF vulnerability using the Aegis DataBinding in versions of Apache CXF before 4.0.4, 3.6.3 and 3.5.8 allows an attacker to perform SSRF style attacks on webservices that take at least one parameter of any type. Users of other data bindings (including the default databinding) are not impacted.
GitHub Security Advisory: GHSA-qmgx-j96g-4428
Package: org.apache.cxf:cxf-rt-databinding-aegis (MAVEN)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: >= 3.6.0, < 3.6.3
Patched in: 3.6.3

Summary: SSRF vulnerability using the Aegis DataBinding in Apache CXF

Details:
A SSRF vulnerability using the Aegis DataBinding in versions of Apache CXF before 4.0.4, 3.6.3 and 3.5.8 allows an attacker to perform SSRF style attacks on webservices that take at least one parameter of any type. Users of other data bindings (including the default databinding) are not impacted.