ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Welcome to 2017! Our new year resolution: continue to provide you the safest, most secure way to protect your data!
Today Nextcloud makes available updates for Nextcloud 9, 10 and 11 with a number of bug fixes and a precautionary update for the SwiftMailer vulnerability discovered recently. We recommend to update at your earliest convenience. Read on to find out what has changed.
Nextcloud 11.0.1 introduces about two dozen fixes dealing with Safari’s lack of decent CSPv3 support, a fix for LDAP issues, the Calendar/Contact DAV endpoint and more. About a dozen is relevant for 10.0.3, making updates more reliable and fixing some translation and visual issues.
Find more details in our changelogs.
Just before the end of 2016, a security researcher published a security advisory for an unfixed critical vulnerability in SwiftMailer. SwiftMailer is a widely used library for sending e-mails from PHP applications and used by many popular frameworks such as Yii2, Laravel or Symfony.
This library in question is also used by Nextcloud and we’ve immediately begun analyzing the vulnerability as well as it’s exploitation path. After extensive analysis by members of our security team we believe that a standard Nextcloud server installation is not affected by this specific vulnerability. However, as we include the library in our public programming API third-party app authors may call the library in an exploitable way.
Nextcloud takes security very seriously and protecting user data is of utmost importance to us. We want to state again, that this is purely a security pre-caution and based on our research this seems like a non-exploitable issue in a default Nextcloud server installation. However, as we didn’t want to take even any slightly theoretical chance of exploitation we’ve decided to err on the side of caution to protect our users.
Nextcloud employs dedicated security personnel, is subject to regular penetration testing, static and dynamic analysis and offers bug bounties up to $5,000 for critical security vulnerabilities.
Learn more about Nextcloud security…
We made available the updates for Nextcloud 9, 10 and 11 on our download server and via the updater. If you are on the latest version you will receive an update notification. Due to staged roll-outs the update notification does not come at once for all users. You can expect to be notified at the latest by the end of next week. Users on Nextcloud 10 or 11 can bypass the waiting period by setting their release channel to ‘beta’ to immediately receive Nextcloud 11.0.1.
We recommend to update at your earliest convenience. Get the latest Nextcloud 11 from our download page and earlier releases from the changelog page.
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
Ver más
When cables are cut, sanctions are put in place or privacy legislation prohibits the use of the service your entire organization depends on, what can you do? Amidst geo-political changes, organizations face dependencies on large, centralized communication platforms. A major example of this is the SaaS-only communication platform Microsoft Teams. It is the only solution […]
Ver más
In Nextcloud Hub 8, we introduced interactive widgets, a completely new mechanic that lets you share, access and interact with items from various apps in a compact widget format throughout your platform.
Ver más
