Hello everyone,
The next Language Community Meeting is happening soon, on Friday, November
20th at 16:00 UTC! If you would like to join, simply sign up on the wiki
page
<https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/…>
.
This is a participant-driven meeting for sharing updates on
language-related projects, discussing technical challenges in language
wikis, and collaborating on solutions. At the upcoming meeting, we’ll hear
from Herschal Jackson (WMZA) on "The Four Roles Every Language Wiki Needs".
We’ll also have an update from the WMF Language & Product Localization team
about a new collaboration with Stanford University’s SILICON initiative.
This collaboration will involve pilot Wikimedia language communities
contributing foundational language data to Unicode’s Common Locale Data
Repository (CLDR).
Got a topic to share? Whether it’s a technical update from your project, a
challenge you need help with we’d love to hear from you! Feel free to reply
to this message or add agenda items to the document here
<https://etherpad.wikimedia.org/p/language-community-meeting-nov-2026>.
The 12th edition of the Language & Internationalization Newsletter (October
2026)
<https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/…>
is also now available. This newsletter provides updates from the
July–September 2026 quarter, including new feature development,
improvements across various language-related projects and support efforts,
details about community meetings, and ideas for contributing to projects.
We look forward to your ideas and participation at the Language Community
Meeting. See you there!
Feel free to translate this message into your local language and share it
on your village pump or other community channels to help spread the word.
Cheers,
Srishti
Srishti Sethi (she / her)
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello again -
A new security issue regarding NodeJS [0][1] has come to the attention of
the Wikimedia Foundation's Product Safety and Integrity, SRE, and Tools
Platform teams. The working name for this vulnerability is Node2Shell, and
it affects various versions of NodeJS. “If an attacker can get a malicious
payload in front of your app, the flaw can crash the process, leak part of
its memory, or potentially let them run their own code.”
If you host a Node project on Toolforge or Cloud VPS, you should
immediately confirm whether your project is running a vulnerable version of
Node, which would be any version previous to Node 22.23.4, 24.22.1 or
26.12.1. You should also review these steps [2] to confirm whether your
project is currently vulnerable. If you determine that your
Toolforge-hosted tool or Cloud VPS project is affected by this issue, you
should disable it until WMCS can provide new, secure NodeJS images for your
service.
Currently, we do not think we need to conduct a central system-wide
shut-down at this time due to the complexity involved in exploiting this
issue. We will continue to monitor the situation and adapt our response as
needed.
We will keep you updated. Thank you again for your understanding and
continued support.
Arthur, on behalf of WMCS.
[0] https://nvd.nist.gov/vuln/detail/cve-2026-111497
[1] https://www.aikido.dev/blog/node2shell-nodejs-brotli-rce-cve-2026-111497
[2]
https://www.aikido.dev/blog/node2shell-nodejs-brotli-rce-cve-2026-111497#ho…
--
*Arthur Reis Puthin* (he/him/his)
Engineering Manager - Tools Platform
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
Our central Puppet servers[0] were down earlier last night and this
morning while we mitigated some security issues[1] found in the Puppet
stack. In addition to the automated emails sent about Puppet run
failures (that you can safely ignore - sorry about those!), this
downtime would have only caused issues for provisioning new instances.
Functionality of existing instances was not affected, and no action is
needed from your part.
[0]: https://wikitech.wikimedia.org/wiki/Help:Puppet
[1]: https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/
taavi + rest of the Cloud VPS admins
--
Taavi Väänänen (he/they)
Site Reliability Engineer, Tools Infrastructure
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello,
Two new Toolforge features are now available for all Toolforge users to try out:
* Toolforge alerts [0]
* Toolforge extended logging capabilities [1]
Toolforge alerts let you receive email notifications when any of your
tools is encountering a common error condition (failing to respond,
responding with errors, or restarting frequently).
Toolforge extended logging capabilities let you retrieve logs for
events like job creation, deletion or deployment failure, with a new
CLI `toolforge logs`, at the same time that you retrieve your job
logs.
Both features are in BETA: you should expect some bugs, and you should
expect some changes to the features themselves. Your feedback is, as
always, very appreciated - you can use our usual communication
channels. [2]
We’ll be monitoring the feedback, bug reports, and related tasks
closely and addressing issues as they arise. We count on your
engagement to ensure the new features are providing the intended
value.
Francesco, on behalf of the Wikimedia Tools Platform team. [3]
[0] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Alerts
[1] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Running_jobs#Toolforge_l…
[2] https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication
[3] https://www.mediawiki.org/wiki/Wikimedia_Tools_Platform_Team
--
Francesco Negri (he/him) -- IRC: dhinus
Site Reliability Engineer, Tools Platform
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…