<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Security Vulnerabilities - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Security Vulnerabilities News feed</description>
    <item>
      <title>npm Staged Publishing Available, Adding a Human Approval Step before Packages Go Live</title>
      <link>https://www.infoq.com/news/2026/08/npm-stage-available/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Security+Vulnerabilities-news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;npm has introduced staged publishing for Node.js, requiring maintainer approval before a version is installable. Versions are queued and must pass a two-factor authentication challenge for release. This feature aims to enhance security amid rising supply chain threats. It is available in npm CLI 11.15.0+ and Node 22.14.0+, alongside new configurable permission flags.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Open Source</category>
      <category>Application Security</category>
      <category>NPM</category>
      <category>Security Vulnerabilities</category>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 06:12:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/npm-stage-available/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Security+Vulnerabilities-news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-08-07T06:12:00Z</dc:date>
      <dc:identifier>/news/2026/08/npm-stage-available/en</dc:identifier>
    </item>
    <item>
      <title>Wiz Discloses CosmosEscape, and Practitioners Debate What Customers Could Have Done</title>
      <link>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Security+Vulnerabilities-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/cosmosescape-master-key/en/headerimage/generatedHeaderImage-1785835623595.jpg"/&gt;&lt;p&gt;Wiz Research disclosed CosmosEscape, a chain that escaped Azure Cosmos DB's Gremlin sandbox and reached a platform-wide key granting read and write access to every database on the service. Microsoft blocked the entry point within two days but took until July 2026 to remove the key. Practitioners debated shared responsibility and what that rearchitecture actually cost.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Access Control</category>
      <category>Azure</category>
      <category>Multi-Tenant Data</category>
      <category>Cloud</category>
      <category>Cloud Architecture</category>
      <category>Database</category>
      <category>Security Vulnerabilities</category>
      <category>Multi-tenancy</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 09:21:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Security+Vulnerabilities-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-06T09:21:00Z</dc:date>
      <dc:identifier>/news/2026/08/cosmosescape-master-key/en</dc:identifier>
    </item>
  </channel>
</rss>
