Version 2026.11.20.1 #514

Merged
jcoffey-dev merged 1 commits from release/version-2026.11.20.1 into release/2026 2026-11-20 21:14:09 +00:00
2 changed files with 34 additions and 1 deletions

No files matched your search

+33
View File
@@ -11,6 +11,39 @@ https://github.com/inbuxa/inbuxa-server/security/advisories.
Every version PR adds that version's entry here. CI refuses a version this
file has no entry for (`tools/release/changelog-check.py`).
## [2026.11.20.1] - 2026-11-20
2026.11.20 with 2 security fixes from a private security review (1 high,
1 medium) and one hardening change. 2026.x up to and including 2026.11.20
is affected. The same fixes are in 27.1-rc.37.
### Security
High
- WebDAV: an uploaded HTML or SVG file ran as a page of the server's
origin when opened in a browser. Every WebDAV file answer now carries
`Content-Security-Policy: default-src 'none'; frame-ancestors 'none';
sandbox` and `nosniff`; only raster images, audio, video and plain text
are shown inline, everything else downloads. (GHSA-v4c6-686h-h927, #512)
Medium
- Multi-tenancy: a tenant administrator could make the server send
requests to internal addresses through an ACME or DNS provider. A
tenant's providers now reach only public addresses (HTTPS for ACME and
HTTP-based DNS providers), RFC 2136 servers must be public, and fields
built into URLs must be plain names. ACME errors carry only the problem
type and detail. (GHSA-qmc9-xcrm-w836, #512)
### Changed
- A tenant's OIDC directory reaches only public HTTPS addresses,
discovered endpoints included. (#512)
### Upgrading
- WebDAV: HTML, SVG, XML, PDF and untyped files now download instead of
opening in the browser.
- Tenant-owned ACME providers, DNS providers and OIDC directories at a
private, loopback or plain-HTTP address stop working; move them to a
public HTTPS address, or have a server administrator own them.
## [2026.11.20] - 2026-11-20
### Changed
+1 -1
View File
@@ -87,7 +87,7 @@ fn legacy_setting(name: &str, is_set: impl Fn(&str) -> bool) -> Option<String> {
#[macro_export]
macro_rules! brand_version {
() => {
"2026.11.20"
"2026.11.20.1"
};
}