Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

Security

34 Topics 297 Posts

Discussion and info about security related topics

Scheduled critical security release for PHP
More details here: PHP scheduled critical security release CVE-2026-115560
  • 1 Votes
    2 Posts
    35 Views
    jamesJ
    Hello @osobo Because of all the new CVEs thanks to LLMs I have started to use https://dependencytrack.org/. I am still only tinkering with it and validating if we can use it in our Cloudron development and packaging workflows. With that information, I have checked my dependency track dashboard for cloudron/python-base tag 3.12-20261023 and cloudron/base tag 6.0.1. @osobo said: Docker Scout reports 10 critical and 74 high findings Interesting! Dependency track shows the following for the base image: [image: deptrack.cloudron.dev_projects_f21919f2-20d4-4a9f-96c5-6e379ee18096_findings.jpeg] So your report from Docker Scout is 10 critical, but dependency track found 28 critical, 134 high, 119, medium, 41 low and 71 unassigned. Dependency track also has a view for Exploit Predictions with a KEV value if a CVE is actively exploited in the wild. From that data I have from decency track my findings are the following: None of the CVEs in cloudron/base:6.0.1 or cloudron/python-base:3.12-20261023 are on the CISA KEV catalog or the ENISA EU KEV list. Nothing is known to be exploited in the wild. The EPSS scores are low. The highest is 0.065 (6.5% chance of exploitation activity in the next 30 days). 461 of 489 findings score below 0.01 (1%). Top 5 by EPSS: EPSS ID Package 0.065 UBUNTU-CVE-2026-123633 nginx 1.28.3-2ubuntu1.11 0.064 UBUNTU-CVE-2026-123007 nginx 1.28.3-2ubuntu1.11 0.054 CVE-2007-0770 graphicsmagick 1.3.46 0.040 CVE-2026-45447 openssl 3.5.5-1ubuntu3.7 0.023 CVE-2025-61726 Go stdlib 1.24.6 The GraphicsMagick entry is a 2007 CVE matched against a 2025 release, so most likely a false match. cloudron/python-base:3.12-20261023 only adds 8 packages on top of cloudron/base:6.0.1 (python3.12 3.12.15 and pip 26.2.2), and Dependency-Track has no findings for them. The python3.12 packages are not from the Ubuntu archive (version suffix +resolute1), so the Ubuntu advisories may not cover them. Why the numbers differ from Docker Scout? Dependency-Track only sees the final filesystem of the image. Binaries deleted in a later layer, like the gosu, yq and pebble you mentioned, do not show up at all. Scout reports them from the lower layers. The vulnerability sources also differ, so the counts are not directly comparable. So yes, there are CVEs, but nothing known exploited and nothing with a high exploit prediction. They get fixed with the regular base image updates. The two nginx findings at the top are both HTTP/2 bugs (CVE-2026-123633, CVE-2026-123007). On Cloudron the host nginx terminates TLS and HTTP/2 and proxies to the app container over HTTP/1.1, so the nginx inside the container never receives HTTP/2 traffic. For these two, the host nginx is the one that matters, and it is updated through the host OS, not the base image. Why a CVE in an image does not automatically mean a Cloudron app is affected A scanner lists every package with a known CVE. Whether that CVE can actually be used against a Cloudron app depends on how the app runs, in this case for the NGINX CVE: Reverse proxy: the host nginx handles TLS and HTTP/2 and passes requests to the app container over plain HTTP/1.1. Bugs in the TLS or HTTP/2 code of a package inside the container (like the two nginx CVEs above) cannot be reached that way Container hardening: apps run with a read-only root filesystem, a restrictive AppArmor profile and their own Docker network Host updates: Cloudron enables unattended-upgrades on the host, so Ubuntu security fixes for the host (including the host nginx) are installed automatically Each of these layers narrows which vulnerabilities are reachable at all, which is why scanner counts alone overstate the real risk. It also makes checking a single CVE more work, because the answer depends on the package, how it is used, and which layer sits in front of it. These layers do not protect against bugs in an app's own code, since those arrive inside normal requests. Those are fixed by updating the app package, which is why keeping apps updated (automatic updates are on by default) matters most. What we are doing I am continuing the evaluation of Dependency-Track for Cloudron, so we can see which images are affected by new CVEs, which of those are known to be exploited (KEV) and which have a high exploit prediction (EPSS). The goal is to fix the ones that matter first, instead of sorting through hundreds of scanner findings by hand. It is still early, but it already helped to answer this thread with data instead of guesses. If you find something that looks exploitable on Cloudron, please report it privately to security@cloudron.io.
  • WordPress 7.1.5 Fixes 20 Security Flaws

    2
    5 Votes
    2 Posts
    68 Views
    girishG
    Packages are out with the fix .
  • PHP scheduled critical security release CVE-2026-115560

    8
    3 Votes
    8 Posts
    441 Views
    girishG
    Many LAMP app updates are already out (especially the big ones like WP, Nextcloud).
  • ruby2ßhell

    5
    2 Votes
    5 Posts
    119 Views
    girishG
    Yup, mastodon is already out. We are releasing the updates as soon as the upstream fixes them.
  • 2 Votes
    3 Posts
    164 Views
    nichu42N
    Luckily, it's fixed in the meantime. But it took forever. Not exactly good PR for Canonical. My desktop had the fix already when the CVE was published.
  • Java4Shell CVE-2026-114938

    Moved
    6
    2 Votes
    6 Posts
    417 Views
    girishG
    Most of the packages are updaetd now . Some like urlaubsverwaltung are on the way.
  • Forgejo security release is scheduled for today

    2
    1 Votes
    2 Posts
    70 Views
    girishG
    Forgejo 17.0.2 fixed the bug (https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/17.0.2.md) and the Cloudron package is out now.
  • nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.)

    Moved Solved nginx security
    16
    2 Votes
    16 Posts
    517 Views
    W
    @jdaviescoates said: 1.24.0-2ubuntu7.20 Me too. Those are recent updates though, and it looks like they include patches for nginx2root: https://launchpad.net/ubuntu/+source/nginx/1.24.0-2ubuntu7.20
  • mod_http security issue (CVE-2026-119618)

    Moved
    3
    3 Votes
    3 Posts
    201 Views
    G
    @girish Thanks for the quick clarification, that is great news!
  • Security issue thread - PHP and eMudhra cert compromise

    Moved
    121
    19 Votes
    121 Posts
    14k Views
    jamesJ
    Hello @recliner2042 Baserow already fixed the issue https://github.com/baserow/baserow/pull/6494, but it is not yet released.
  • 2 Votes
    3 Posts
    300 Views
    imc67I
    @james thanks! Related: cloudron/php-base:8.5-20261021 and the current WordPress package (3.17.1) still ship libbrotli1 1.2.0-3build1, while the Ubuntu fix for CVE-2026-111497 is 1.2.0-3ubuntu0.1. PHP apps reach this through libcurl, as WordPress decodes Brotli on outbound requests (see Patchstack's write-up, https://patchstack.com/articles/wordpress-doesnt-ship-brotli-its-still-exposed-to-cve-2026-111497/). Could the PHP base get a rebuild as well?
  • NodeJS CVE

    Moved
    5
    0 Votes
    5 Posts
    391 Views
    H
    @nebulon sorry to jump in here. CVE-2026-111497 is not just about NodeJS ( that node2shell name isn't great) but potentially anything using the same brotli decoder. i.e. this page https://broccoli2shell.com/ gives an overview of software embedding libbrotli copy (similar as the 'fun' we had recently with the embedded ca-certs) Looking at the 6.0.1 base-image it doesn't contain the libbrotli1 version with the Ubuntu fix yet (1.2.0-3ubuntu0.1) as that came just a few days later only Looking what points to it (apt-rdepends) apache2 (php container, but maybe less critical given the nginx as proxy on the host) curl non-http things (libwoff1, jxl (maybe via ffmpeg) That's not a full or verified list just a first look. Note: I'm also not shouting critical here just writing as above only talked about NodeJS angle. Do you plan to bump the base image again for this? Otherwise are the any plans to do that periodically to catch up to accumulated fixes which don't warrant the overhead of some immediate action?
  • CVE-2026-110264 - Critical Patch 19.5.1

    Moved
    3
    2 Votes
    3 Posts
    202 Views
    milian.hackradtM
    Thanks for pushing the update, I have successfully applied it to our customers Cloudron GitLab instance.
  • 4 Votes
    14 Posts
    3k Views
    P
    @joseph Yes, is better to have one main thread
  • Affected: Copy Fail CVE-2026-31431

    Moved ubuntu security cve
    3
    3 Votes
    3 Posts
    2k Views
    J
    https://cert.europa.eu/publications/security-advisories/2026-005/ is maybe a better link
  • Important Security Patch: 2.13.3 and 1.123.27

    Moved
    3
    0 Votes
    3 Posts
    742 Views
    U
    Glad to hear it! Thanks @nebulon.
  • Should I worry about MongoDB Vulnerability CVE-2025-14847

    Moved
    4
    1 Votes
    4 Posts
    873 Views
    girishG
    We already fixed this - https://git.cloudron.io/platform/box/-/commit/a02e933375e5ef6b833029acee1bae969e1203fe . We are working on a final update to 9.0 with various UI fixes and this change will be part of that (i.e 9.0.16).
  • 1 Votes
    2 Posts
    1k Views
    jamesJ
    Hello @zonzonzon The current latest version in the Cloudron app store 2.1.2 is not effected. Also, the latest N8N version for the old 1.123.7 is also not effected. If you have your N8N updated to the last 1.123.7 or 2.1.2 version, then you are save.
  • 4 Votes
    2 Posts
    421 Views
    No one has replied
  • How to update Redis vulnerable version (#RediShell) ?

    Moved Solved redis security
    4
    3 Votes
    4 Posts
    2k Views
    girishG
    I updated redis to 8.2.2 - https://git.cloudron.io/platform/box/-/commit/3547be34010a737d9fbd5aed5bb9e787eeff5456