MikolajBalcerek opened a new pull request, #45743:
URL: https://github.com/apache/superset/pull/45743

   ### SUMMARY
   
   Bump brotli to avoid scanners complaining about CVEs.
   
   Brotli 1.0.3–1.2.0 has an out-of-bounds write in its decoder: 
[CVE-2026-111497](https://nvd.nist.gov/vuln/detail/CVE-2026-111497) 
([GHSA-9v8h-qqgm-4m35](https://github.com/advisories/GHSA-9v8h-qqgm-4m35), 
[PYSEC-2026-4322](https://github.com/pypa/advisory-database/tree/main/vulns/brotli/PYSEC-2026-4322.yaml)).
   
    It is fixed in 
[1.2.1](https://github.com/google/brotli/releases/tag/v1.2.1).
   
   Superset pins `brotli==1.2.0`. Bumps the floor.
   
   Exploitation looks very difficult to do, you need to make Superset make HTTP 
request to a server that sends poisoned response
   
   
   ### Testing
   - In an installed environment: `python -c "import brotli; 
print(brotli.__version__)"` → `1.2.1`.
   - I have added the same pin on top of the 6.1.0 envs and 7.0.0rc2 and didn't 
see a regression.
   
   
   ### BTW
   - https://github.com/apache/arrow/issues/55166 once pyarrow is fixed, it 
would be good to bump pyarrow in Superset as well
   - via pyarrow, in theory you could do a Database Upload file => fabricated 
parquet => get a denial-of-service/RCE. But low priority too, since you need to 
be an user able to upload to DB on Superset, DB has to allow uploads, ...
   - - https://github.com/ClickHouse/ClickHouse/pull/127419 clickhouse seen DoS 
like this
   -  you could turn off "Allow file uploads" to be safe
   
   
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to