<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: kozhevniko</title>
    <description>The latest articles on DEV Community by kozhevniko (@kozhevniko).</description>
    <link>https://dev.to/kozhevniko</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4125316%2Ffd669e89-7ad5-4a22-8b23-6e0990d00d7f.png</url>
      <title>DEV Community: kozhevniko</title>
      <link>https://dev.to/kozhevniko</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kozhevniko"/>
    <language>en</language>
    <item>
      <title>Miren Runtime Requested Client Certificates Without Verifying the Cluster CA</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:41:12 +0000</pubDate>
      <link>https://dev.to/kozhevniko/miren-runtime-requested-client-certificates-without-verifying-the-cluster-ca-4pj0</link>
      <guid>https://dev.to/kozhevniko/miren-runtime-requested-client-certificates-without-verifying-the-cluster-ca-4pj0</guid>
      <description>&lt;h1&gt;
  
  
  Miren Runtime Requested Client Certificates Without Verifying the Cluster CA
&lt;/h1&gt;

&lt;p&gt;Mutual TLS is an authentication mechanism only when the server validates the certificate chain and maps a verified identity to authorization. CVE-2026-75521 failed the first half of that contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  The defect
&lt;/h2&gt;

&lt;p&gt;Before Miren Runtime 0.11.1, the RPC server on the default QUIC/HTTP3 port &lt;code&gt;8443&lt;/code&gt; requested TLS client certificates with &lt;code&gt;tls.RequestClientCert&lt;/code&gt; but did not verify that a presented certificate chained to the configured cluster certificate authority.&lt;/p&gt;

&lt;p&gt;The advisory states that certificate identities bypassed RBAC and could receive cluster superuser treatment. This is more than accepting a self-signed certificate: an unverified certificate became an administrative identity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Response
&lt;/h2&gt;

&lt;p&gt;Upgrade to 0.11.1 or later. Verify the running version and confirm that the RPC listener rejects a certificate that does not chain to the cluster CA. Add a negative test to the cluster deployment pipeline so a future change cannot silently return to request-only behavior.&lt;/p&gt;

&lt;p&gt;Rotate cluster credentials and review administrative actions during the affected period. Audit certificates issued by the cluster CA, service accounts, role bindings, and API calls made through port &lt;code&gt;8443&lt;/code&gt;. Preserve TLS handshake metadata where available.&lt;/p&gt;

&lt;p&gt;Restrict the RPC port to cluster administration networks even after patching. Network controls are not an identity control, but they reduce the population that can reach the listener.&lt;/p&gt;

&lt;h2&gt;
  
  
  Engineering lesson
&lt;/h2&gt;

&lt;p&gt;Certificate presence, certificate validity, chain verification, allowed key usage, and authorization mapping are separate checks. A server must fail closed when any required check is absent. Logging should record the verified identity and issuer, never an unverified common name as though it were authenticated.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/mirendev/runtime/security/advisories/GHSA-8fh7-7q4q-cq52" rel="noopener noreferrer"&gt;Miren Runtime advisory&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/mirendev/runtime/releases/tag/v0.11.1" rel="noopener noreferrer"&gt;Miren Runtime v0.11.1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.openadvisories.org/vuln/CVE-2026-75521" rel="noopener noreferrer"&gt;CVE-2026-75521 record&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
      <category>mirenruntime</category>
      <category>cve202675521</category>
    </item>
    <item>
      <title>Tableau Server Exposure Needs a Site-Role and Content-Permission Review</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Fri, 20 Nov 2026 01:22:27 +0000</pubDate>
      <link>https://dev.to/kozhevniko/tableau-server-exposure-needs-a-site-role-and-content-permission-review-50i4</link>
      <guid>https://dev.to/kozhevniko/tableau-server-exposure-needs-a-site-role-and-content-permission-review-50i4</guid>
      <description>&lt;h1&gt;
  
  
  Tableau Server Exposure Needs a Site-Role and Content-Permission Review
&lt;/h1&gt;

&lt;p&gt;Tableau Server can contain workbooks, data sources, projects, extracts, and connection information. A public Tableau surface is therefore a data-governance question, not just an application inventory item.&lt;/p&gt;

&lt;h2&gt;
  
  
  Count context
&lt;/h2&gt;

&lt;p&gt;On 2026-11-20, ZoomEye returned 161,882 matches for &lt;code&gt;app="Tableau Server"&lt;/code&gt; and 7,161 for &lt;code&gt;title="Tableau"&lt;/code&gt; with &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. The large application count needs careful interpretation because product fingerprints can be broad and may not isolate every deployment shape.&lt;/p&gt;

&lt;p&gt;The title count is narrower but misses many products. Both numbers are discovery signals, not vulnerable-server counts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Authorization model
&lt;/h2&gt;

&lt;p&gt;Tableau authorization combines license level, site role, and permissions on assets such as projects, workbooks, and data sources. Permissions are asset-based and implicitly deny access unless granted to a user or group.&lt;/p&gt;

&lt;p&gt;Server Administrator has broad access, while Site Administrator roles are scoped to one site. A locked project can enforce default permissions across descendants. Review these scopes separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Triage path
&lt;/h2&gt;

&lt;p&gt;Confirm the site boundary and authentication method. Review server and site administrators, project locks, guest access, and the permissions on data sources that contain stored connection credentials.&lt;/p&gt;

&lt;p&gt;Check whether users can download data, refresh extracts, or change ownership. A user who cannot edit a workbook may still extract its data or connection metadata.&lt;/p&gt;

&lt;h2&gt;
  
  
  Monitoring
&lt;/h2&gt;

&lt;p&gt;Alert on new server or site administrators, project permission changes, data-source ownership changes, and unusual extract refreshes. Correlate Tableau audit events with database authentication logs.&lt;/p&gt;

&lt;p&gt;ZoomEye supplies external discovery. Tableau's site roles and asset permissions provide the internal evidence needed to assess exposure.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://help.tableau.com/current/server/en-us/security_authorize.htm" rel="noopener noreferrer"&gt;Tableau Server authorization&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://help.tableau.com/current/server/en-us/users_site_roles.htm" rel="noopener noreferrer"&gt;Tableau users and site roles&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
      <category>tableauserver</category>
      <category>apptableauserver</category>
    </item>
    <item>
      <title>Fluidd Inherits Moonraker Trust, Including the Defaults Around It</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 22:02:15 +0000</pubDate>
      <link>https://dev.to/kozhevniko/fluidd-inherits-moonraker-trust-including-the-defaults-around-it-54e8</link>
      <guid>https://dev.to/kozhevniko/fluidd-inherits-moonraker-trust-including-the-defaults-around-it-54e8</guid>
      <description>&lt;h1&gt;
  
  
  Fluidd Inherits Moonraker Trust, Including the Defaults Around It
&lt;/h1&gt;

&lt;p&gt;Fluidd is a web interface for Klipper and Moonraker. It can view printer state, manage files, and send commands through the Moonraker API. That makes the interface part of a physical control path. A login prompt is not the only security question. The API's trusted-client rules and the network around the printer determine what an unauthenticated or weakly authenticated client can do.&lt;/p&gt;

&lt;p&gt;At 05:44:59 CST on 20 November 2026, &lt;code&gt;title="Fluidd"&lt;/code&gt; returned 6,179 matches with &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. This is a title-level index observation. It does not prove that a match is a live printer or that its API is exposed. Common interface names can produce a broad result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Authentication belongs to Moonraker
&lt;/h2&gt;

&lt;p&gt;Fluidd documentation states that authorization uses Moonraker's authentication endpoints. A deployment can add users, enable &lt;code&gt;force_logins&lt;/code&gt;, and define trusted clients. The documentation also notes that a fresh installation may treat the local client as trusted, and that &lt;code&gt;force_logins: false&lt;/code&gt; can cause Moonraker to rely on &lt;code&gt;trusted_clients&lt;/code&gt; first. Those defaults explain why a printer that works on a home LAN can behave differently when a reverse proxy or remote tunnel exposes it.&lt;/p&gt;

&lt;p&gt;Review the effective Moonraker configuration, not only the Fluidd settings page. List trusted networks, user accounts, API keys, and the exposure path from the internet. If remote access is required, terminate it at a strong identity-aware proxy and disable direct public access to Moonraker. Do not treat a hidden URL as authentication.&lt;/p&gt;

&lt;h2&gt;
  
  
  The physical consequence changes the response
&lt;/h2&gt;

&lt;p&gt;A printer command can heat a tool, move an axis, or start a print. The safety consequence is not the same as reading a status dashboard. Separate read-only access from command authority where the deployment allows it. Protect configuration files that can change macros, update repositories, or add services. A compromised printer interface can also become a foothold on the local network.&lt;/p&gt;

&lt;p&gt;Review firmware and add-on update sources. Fluidd itself is a web client, while Moonraker and Klipper provide the API and machine control. The supply chain spans all three. Pin update sources, inspect release notes, and keep a recovery image for the printer controller.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use the count for inventory hygiene
&lt;/h2&gt;

&lt;p&gt;Do not probe an unknown printer just because its title appears in a search result. The 6,179 matches are a reason to reconcile owned DNS names, reverse-proxy entries, and public hostnames. A legitimate public status page should expose only the intended view. An administrative Fluidd page should not share the same unauthenticated path.&lt;/p&gt;

&lt;p&gt;Check certificate names and proxy rules. A misconfigured proxy can route a public hostname to the printer API while the intended dashboard is read-only. Test the authentication redirect, API behavior without a token, and the trusted-client path from outside the expected network.&lt;/p&gt;

&lt;h2&gt;
  
  
  A safe verification sequence
&lt;/h2&gt;

&lt;p&gt;In a lab deployment, enable a user, set &lt;code&gt;force_logins&lt;/code&gt;, and remove broad trusted-client ranges. Confirm that a new client must authenticate and that a command endpoint rejects an unauthenticated request. Add a token, verify the expected command scope, revoke it, and repeat. Keep the test limited to a harmless command or a simulator.&lt;/p&gt;

&lt;p&gt;Fluidd is a useful control panel when its trust model matches the network. The external count is not the control. The control is the effective Moonraker authorization, the proxy path, and the person who can explain why an internet-facing printer surface exists at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/fluidd-core/fluidd" rel="noopener noreferrer"&gt;Fluidd project overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/Snapmaker/u1-fluidd/blob/main/docs/authorization/index.md" rel="noopener noreferrer"&gt;Fluidd authorization documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/Arksine/moonraker/blob/master/docs/configuration.md" rel="noopener noreferrer"&gt;Moonraker configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/Arksine/moonraker/blob/master/docs/external_api/server.md" rel="noopener noreferrer"&gt;Moonraker external API&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/" rel="noopener noreferrer"&gt;ZoomEye&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
    </item>
    <item>
      <title>An incident response checklist for possible CVE-2026-113867 account abuse</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 18:41:18 +0000</pubDate>
      <link>https://dev.to/kozhevniko/an-incident-response-checklist-for-possible-cve-2026-113867-account-abuse-4lf3</link>
      <guid>https://dev.to/kozhevniko/an-incident-response-checklist-for-possible-cve-2026-113867-account-abuse-4lf3</guid>
      <description>&lt;h1&gt;
  
  
  An incident response checklist for possible CVE-2026-113867 account abuse
&lt;/h1&gt;

&lt;p&gt;An investigation into CVE-2026-113867 should begin with a version and configuration question, then move to account history only when the relevant XMPP path was present. The flaw could inject outbound stanzas through Thunderbird, but the reviewed sources do not show a universal compromise marker. A disciplined timeline can separate vulnerable systems from confirmed abuse.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vulnerability overview
&lt;/h2&gt;

&lt;p&gt;Mozilla documented CVE-2026-113867 in MFSA 2026-114 and MFSA 2026-115. Thunderbird did not escape attribute values when serializing outgoing XMPP stanzas. Incoming request values echoed through automatic replies could inject arbitrary stanzas into the authenticated connection.&lt;/p&gt;

&lt;p&gt;The flaw was fixed in Thunderbird 158.0.1 and 153.5.1. Mozilla assigns high impact. CISA ADP's CVSS 3.1 score is 9.1, and SUSE lists a 5.3 CVSS 3.1 score plus a 6.9 CVSS 4.0 score. No reviewed source confirms in-the-wild exploitation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mechanism and exploitation conditions
&lt;/h2&gt;

&lt;p&gt;A remote XMPP user sends crafted input to a vulnerable Thunderbird client. The client later generates an automatic reply and copies incoming values into an outbound attribute without proper escaping. The resulting XML can contain additional stanzas.&lt;/p&gt;

&lt;p&gt;The XMPP server processes those stanzas as actions from the signed-in user. Mozilla says the attacker could send messages or change contact and subscription settings. The victim does not need to interact after the reply path is triggered.&lt;/p&gt;

&lt;p&gt;Only Thunderbird's XMPP chat feature is in scope. Investigators should confirm that the endpoint had an affected build and an XMPP account. A patched build or a client without XMPP use weakens the case for this CVE as the cause of an unexplained message.&lt;/p&gt;

&lt;h2&gt;
  
  
  Impact
&lt;/h2&gt;

&lt;p&gt;The principal risk is misuse of the user's identity in XMPP. Messages can mislead contacts, and roster or subscription changes can alter trust and presence. Because the server accepts the connection as authenticated, the activity may look like normal user behavior.&lt;/p&gt;

&lt;p&gt;The published advisories do not establish code execution, mailbox access, or server compromise. Investigators should separate those outcomes from account-integrity effects until other evidence supports them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Affected products and scope
&lt;/h2&gt;

&lt;p&gt;Review Thunderbird installations below 158.0.1 on the current branch and below 153.5.1 on the older branch. Managed software inventories should verify the actual executable or package build after restart.&lt;/p&gt;

&lt;p&gt;CERT-In's CIVN-2026-0531 groups several products and CVEs. Use the Mozilla Thunderbird advisories for this specific issue. The presence of a Firefox version from the same bulletin is not evidence that Firefox caused an XMPP stanza injection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exposure context
&lt;/h2&gt;

&lt;p&gt;ZoomEye returned 105 matches for app="Thunderbird" and zero for vul.cve="CVE-2026-113867". Exposure is 105. The result counts product fingerprints and does not prove vulnerable versions, active XMPP accounts, or compromise.&lt;/p&gt;

&lt;p&gt;Use endpoint and identity inventory to answer internal scope. The public count is context for product visibility, while server-side XMPP records and client version data are better evidence for an incident.&lt;/p&gt;

&lt;h2&gt;
  
  
  Remediation and mitigations
&lt;/h2&gt;

&lt;p&gt;Patch to Thunderbird 158.0.1 or later, or to 153.5.1 or later on the legacy branch. Restart and verify the running version. If the update is delayed, disable unused XMPP accounts and reduce automatic reply exposure as temporary controls.&lt;/p&gt;

&lt;p&gt;For a suspected incident, preserve XMPP server logs, authentication records, presence changes, subscription changes, and outbound message history before cleanup. Interview the account owner about expected contacts and messages. Record the endpoint build and whether XMPP was enabled at the relevant time.&lt;/p&gt;

&lt;p&gt;Review active sessions and account settings with the XMPP provider. Restore only changes that evidence shows were unauthorized. If forged messages were sent, prepare a factual notification for affected contacts. Close the response only when the client is patched, account state is reviewed, and any residual uncertainty is documented.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://www.mozilla.org/en-US/security/advisories/mfsa2026-114/" rel="noopener noreferrer"&gt;Mozilla MFSA 2026-114&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.mozilla.org/en-US/security/advisories/mfsa2026-115/" rel="noopener noreferrer"&gt;Mozilla MFSA 2026-115&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.suse.com/security/cve/CVE-2026-113867.html" rel="noopener noreferrer"&gt;CVE-2026-113867 score details at SUSE&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&amp;amp;VLCODE=CIVN-2026-0531" rel="noopener noreferrer"&gt;CERT-In CIVN-2026-0531&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>vulnerability</category>
      <category>thunderbird</category>
      <category>xmpp</category>
    </item>
    <item>
      <title>CVE-2026-111181 Operational Response for Node.js Middleware</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 15:21:04 +0000</pubDate>
      <link>https://dev.to/kozhevniko/cve-2026-111181-operational-response-for-nodejs-middleware-f5a</link>
      <guid>https://dev.to/kozhevniko/cve-2026-111181-operational-response-for-nodejs-middleware-f5a</guid>
      <description>&lt;h1&gt;
  
  
  CVE-2026-111181 Operational Response for Node.js Middleware
&lt;/h1&gt;

&lt;p&gt;An effective response to CVE-2026-111181 starts with a precise question: which deployed Node.js services load an affected &lt;code&gt;body-parser&lt;/code&gt; release, and can a compressed request reach that parser? The vulnerability is a network-reachable process crash, so a package version without runtime configuration data is only part of the answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vulnerability overview
&lt;/h2&gt;

&lt;p&gt;The issue is a high-severity denial-of-service vulnerability in &lt;code&gt;body-parser&lt;/code&gt;, published by the Express security team and recorded in GitHub as GHSA-27r3-jxmh-p828. CVE-2026-111181 has a CVSS 3.1 score of 7.5 with vector &lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H&lt;/code&gt;, and the weakness is CWE-248.&lt;/p&gt;

&lt;p&gt;Affected releases are older than 1.20.9 and versions 2.0.0 through 2.3.0. Fixed releases are 1.20.9 and 2.4.0. A request that advertises a compressed body and then supplies trailing bytes can cause an uncaught stream error after the parser has completed the normal body read.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mechanism and exploitation conditions
&lt;/h2&gt;

&lt;p&gt;The parser creates a decompression stream and connects the request to it. It reads the decoded request body and calls the next middleware while the decoder may remain connected. The successful read has detached its error listeners. Trailing data after a valid compressed member then reaches the decoder and raises an error after completion.&lt;/p&gt;

&lt;p&gt;The pipe re-emits the exception, and the Node.js process exits because the application has no handler for the late error. A matching route is unnecessary when parsing is global before routing. Authentication is not consulted when the parser runs before the auth middleware. The attacker needs network access to a reachable parser path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Impact
&lt;/h2&gt;

&lt;p&gt;The immediate consequence is worker availability. An orchestrator may restart the process, but repeated triggers can keep the service in a failure cycle and distract monitoring with generic restart alerts. The CVSS vector records no confidentiality or integrity impact, so the investigation should focus on process termination and service disruption.&lt;/p&gt;

&lt;p&gt;The availability impact can spread beyond the target route. A worker may drop in-flight requests, affect dependent services, and consume capacity while health checks recover. The reviewed reporting described a public reproduction but did not report confirmed in-the-wild exploitation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Affected products and scope
&lt;/h2&gt;

&lt;p&gt;Inventory applications that declare &lt;code&gt;body-parser&lt;/code&gt; directly and applications that receive it transitively. Run &lt;code&gt;npm ls body-parser&lt;/code&gt; in the built application, inspect the lockfile used by the image, and confirm the version inside the deployed container or serverless package. A source check that occurs before packaging is not enough.&lt;/p&gt;

&lt;p&gt;Identify whether the parser is global or attached to selected handlers, whether it processes compressed bodies, and whether it executes before authentication. Those facts determine the practical attack path. The parser may be used with an Express application or a plain Node.js HTTP server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exposure context
&lt;/h2&gt;

&lt;p&gt;ZoomEye Search &lt;code&gt;app="Node.js"&lt;/code&gt; returned 5,569,018 matches. The selected CVE Filter returned 0 for &lt;code&gt;vul.cve="CVE-2026-111181"&lt;/code&gt;. The larger Search count is the Exposure, but it represents Node.js product fingerprints, not confirmed vulnerable middleware.&lt;/p&gt;

&lt;p&gt;The query does not show package versions, Express use, parser placement, or accepted encodings. The zero Filter result does not prove absence. Treat the broad count as a prompt to reconcile internet-facing and internal Node.js services against the dependency inventory.&lt;/p&gt;

&lt;h2&gt;
  
  
  Remediation and mitigations
&lt;/h2&gt;

&lt;p&gt;Update to &lt;code&gt;body-parser&lt;/code&gt; 1.20.9 or later, or 2.4.0 or later, rebuild the deployment artifact, and verify the runtime version. If compressed request bodies are unnecessary, set &lt;code&gt;inflate&lt;/code&gt; to &lt;code&gt;false&lt;/code&gt; so encoded requests are rejected before a decompression stream is created. Test the compatibility effect before deciding to use this workaround.&lt;/p&gt;

&lt;p&gt;Add restart and uncaught-exception alerts, preserve process logs for recurrence analysis, and check that patched images are the ones actually receiving traffic. The reviewed sources provide a public reproduction and a fixed release path. The response should prioritize services that expose the parser to untrusted networks and cannot yet demonstrate a fixed resolved package.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;p&gt;[1] &lt;a href="https://expressjs.com/en/blog/2026-10-28-cve-2026-111181/" rel="noopener noreferrer"&gt;Express security publication&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[2] &lt;a href="https://github.com/advisories/GHSA-27r3-jxmh-p828" rel="noopener noreferrer"&gt;GitHub advisory GHSA-27r3-jxmh-p828&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[3] &lt;a href="https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828" rel="noopener noreferrer"&gt;body-parser advisory&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[4] &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-111181" rel="noopener noreferrer"&gt;NVD record&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[5] &lt;a href="https://github.com/expressjs/body-parser/releases/tag/1.20.9" rel="noopener noreferrer"&gt;body-parser 1.20.9 release&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[6] &lt;a href="https://github.com/expressjs/body-parser/releases/tag/v2.4.0" rel="noopener noreferrer"&gt;body-parser 2.4.0 release&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[7] &lt;a href="https://securityonline.info/body-parser-vulnerability-cve-2026-111181/" rel="noopener noreferrer"&gt;SecurityOnline report&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>javascript</category>
      <category>node</category>
      <category>security</category>
    </item>
    <item>
      <title>AppArmor Exec Transitions Decide Which Profile an Executable Actually Enters</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 12:03:27 +0000</pubDate>
      <link>https://dev.to/kozhevniko/apparmor-exec-transitions-decide-which-profile-an-executable-actually-enters-2a0j</link>
      <guid>https://dev.to/kozhevniko/apparmor-exec-transitions-decide-which-profile-an-executable-actually-enters-2a0j</guid>
      <description>&lt;h1&gt;
  
  
  AppArmor Exec Transitions Decide Which Profile an Executable Actually Enters
&lt;/h1&gt;

&lt;p&gt;An AppArmor profile is not a static label attached to a service forever. When a confined process executes another program, the profile rule can inherit the current confinement, transition to a named profile, or run unconfined. The transition choice is a security decision, and a typo can turn a restrictive service profile into an unconfined child shell.&lt;/p&gt;

&lt;h2&gt;
  
  
  Know the transition classes
&lt;/h2&gt;

&lt;p&gt;AppArmor policy language uses execution rules that combine permission to execute with a transition mode. The AppArmor documentation describes &lt;code&gt;ix&lt;/code&gt; as inheriting the current profile, &lt;code&gt;px&lt;/code&gt; as entering a named profile, &lt;code&gt;cx&lt;/code&gt; as entering a child profile, and &lt;code&gt;ux&lt;/code&gt; as executing unconfined. &lt;code&gt;pux&lt;/code&gt; and related fallback forms can behave differently when the target profile is absent.&lt;/p&gt;

&lt;p&gt;Treat every executable path in a service profile as a transition review. Record the expected target profile for shells, interpreters, helper binaries, package managers, and user-controlled scripts. If a script is writable by a less trusted account, a &lt;code&gt;px&lt;/code&gt; or &lt;code&gt;ix&lt;/code&gt; rule may allow that account to influence what code the confined service runs.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;ux&lt;/code&gt; deserves special attention because it removes confinement for the executed program. It can be useful for carefully bounded administrative workflows, but it should not appear casually in a network-facing service profile.&lt;/p&gt;

&lt;h2&gt;
  
  
  Audit paths and attachments
&lt;/h2&gt;

&lt;p&gt;Start with the executable paths that appear in &lt;code&gt;x&lt;/code&gt; rules. Resolve symlinks and check whether the target can be replaced. Confirm the attachment path of the named profile and whether the executed program is actually covered by that profile on the host.&lt;/p&gt;

&lt;p&gt;Profile names can exist while attachments change after a package upgrade. A rule that expects a transition to an application profile may fail or fall back to a less restrictive mode if the profile is missing. Validate the loaded profile set after upgrades and after image changes.&lt;/p&gt;

&lt;p&gt;Review writable locations as part of the same task. A confined service that can write a helper binary and transition to a profile with broader file access can become a privilege path. Directory ownership, mount options, and AppArmor file rules must agree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the real execution
&lt;/h2&gt;

&lt;p&gt;Use &lt;code&gt;aa-status&lt;/code&gt; or the distribution's supported tooling to confirm which profiles are loaded and in what mode. Review audit logs for denied operations and unexpected transitions. Then exercise the actual command path that the service uses, including interpreters and wrappers.&lt;/p&gt;

&lt;p&gt;Do not test only by running the binary as a user from an interactive shell. Service managers, containers, and custom launchers may apply a different attachment or environment. Capture the process label before and after &lt;code&gt;exec&lt;/code&gt;, and compare it with the approved transition.&lt;/p&gt;

&lt;p&gt;For high-risk helpers, add a denial test. Attempt an operation that the target profile should block. A transition that reports success but lands in the wrong profile is more dangerous than an obvious compatibility failure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep policy and deployment together
&lt;/h2&gt;

&lt;p&gt;Store the profile, its expected attachment, and the tested executable set as one reviewed artifact. Include a change procedure for package upgrades that replace binaries or add new helpers. When a transition fallback is used, document why the fallback cannot drop to unconfined unexpectedly.&lt;/p&gt;

&lt;p&gt;AppArmor is most useful when the expected domain is explicit. The review question is not merely whether the service starts. It is which profile the service enters, which profile each child enters, and whether any route through the documented execution path reaches &lt;code&gt;ux&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://gitlab.com/apparmor/apparmor/-/wikis/QuickProfileLanguage" rel="noopener noreferrer"&gt;AppArmor QuickProfileLanguage&lt;/a&gt;, AppArmor project documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://gitlab.com/apparmor/apparmor/-/wikis/aparmor_policy_development_guide" rel="noopener noreferrer"&gt;AppArmor policy development guide&lt;/a&gt;, AppArmor project documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>infrastructure</category>
    </item>
    <item>
      <title>Perses Defaults Make Authentication and the Datasource Proxy One Review</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 08:41:19 +0000</pubDate>
      <link>https://dev.to/kozhevniko/perses-defaults-make-authentication-and-the-datasource-proxy-one-review-2mal</link>
      <guid>https://dev.to/kozhevniko/perses-defaults-make-authentication-and-the-datasource-proxy-one-review-2mal</guid>
      <description>&lt;h1&gt;
  
  
  Perses Defaults Make Authentication and the Datasource Proxy One Review
&lt;/h1&gt;

&lt;p&gt;Perses is an observability dashboard server, but its security-relevant behavior reaches beyond rendering charts. It can proxy requests to datasources, and the current security documentation states that authentication is disabled by default. A reachable Perses API may therefore expose both dashboard management and a path from the server to internal services.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the measurement found
&lt;/h2&gt;

&lt;p&gt;On 2026-11-19, a count-only ZoomEye SDK query used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. &lt;code&gt;app="Perses"&lt;/code&gt; returned zero. &lt;code&gt;title="Perses"&lt;/code&gt; returned 51, and &lt;code&gt;http.body="Perses"&lt;/code&gt; returned 479.&lt;/p&gt;

&lt;p&gt;The low title count is not proof of safety. The body count may include documentation, client assets, and error pages. Conversely, a real Perses deployment may not expose a distinctive title at all. Product identification must be paired with an application response and an owner record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understand the default risk
&lt;/h2&gt;

&lt;p&gt;Perses documentation states that &lt;code&gt;security.enable_auth&lt;/code&gt; is &lt;code&gt;false&lt;/code&gt; in the shipped configuration. In that mode, anyone who can reach the API can create, modify, or delete projects, dashboards, datasources, and secrets. The datasource proxy can also make the server issue requests to any reachable URL and return the response.&lt;/p&gt;

&lt;p&gt;The configuration documentation expands the consequence: a user allowed to create a datasource or use unsaved proxy endpoints may reach services available from the Perses server, including cloud metadata endpoints or the Kubernetes API. That is a server-side request capability, not a dashboard-display issue.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review in two layers
&lt;/h2&gt;

&lt;p&gt;The first layer is authentication and authorization. Confirm &lt;code&gt;security.enable_auth&lt;/code&gt;, the provider configuration, the encryption key source, and the role model. Check whether anonymous access is intentionally allowed and which actions it grants. If authentication is enabled without a proper encryption key or provider, test the complete login and secret-storage path rather than assuming the setting is sufficient.&lt;/p&gt;

&lt;p&gt;The second layer is the datasource proxy. Inventory global, project, and local datasources. For each one, record the target URL or database, authenticated client, owner, scope, and purpose. Restrict datasource creation to a small role. Review whether the proxy can reach metadata services, control planes, or unrelated internal networks.&lt;/p&gt;

&lt;p&gt;SQL proxy mode should also be examined. Documentation describes read-only transaction behavior, but read-only does not mean harmless. A database query can still disclose sensitive records or reveal service topology. Apply database-level least privilege and network controls in addition to the proxy setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate a candidate
&lt;/h2&gt;

&lt;p&gt;Use title and body leads, then confirm through an approved response and ownership record. Do not call resource-changing endpoints or test the proxy against third-party systems. An owner can identify the deployment and confirm its configuration.&lt;/p&gt;

&lt;p&gt;If the service is a sandbox or an internal evaluation instance, verify that it is not reachable from untrusted networks. If it is production, review authentication, secrets, datasource scope, and network egress together.&lt;/p&gt;

&lt;p&gt;The measured counts are small compared with broad infrastructure products, but size is not the decision. A single unauthenticated Perses instance with a powerful datasource proxy can provide more access than a much larger read-only dashboard inventory.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://perses.dev/docs/perses/latest/security/" rel="noopener noreferrer"&gt;Perses security considerations&lt;/a&gt;, Perses documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://perses.dev/docs/perses/latest/concepts/proxy/" rel="noopener noreferrer"&gt;Perses proxy&lt;/a&gt;, Perses documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://perses.dev/docs/perses/latest/configuration/configuration/" rel="noopener noreferrer"&gt;Perses configuration&lt;/a&gt;, Perses documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;ZoomEye counts: &lt;code&gt;app="Perses"&lt;/code&gt; 0; &lt;code&gt;title="Perses"&lt;/code&gt; 51; &lt;code&gt;http.body="Perses"&lt;/code&gt; 479. &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, pagesize 1, observed 2026-11-19 UTC+8.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>internetmeasurement</category>
      <category>zoomeye</category>
    </item>
    <item>
      <title>A Guest Kernel Raises the Container-Isolation Cost, Not Its Own Guarantee</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 05:20:43 +0000</pubDate>
      <link>https://dev.to/kozhevniko/a-guest-kernel-raises-the-container-isolation-cost-not-its-own-guarantee-3m2p</link>
      <guid>https://dev.to/kozhevniko/a-guest-kernel-raises-the-container-isolation-cost-not-its-own-guarantee-3m2p</guid>
      <description>&lt;h1&gt;
  
  
  A Guest Kernel Raises the Container-Isolation Cost, Not Its Own Guarantee
&lt;/h1&gt;

&lt;p&gt;Traditional containers share the host kernel. Kata Containers changes that arrangement by running a workload in a lightweight virtual machine with its own guest kernel, while presenting a container-like operational model. The result can reduce the reach of a host-kernel compromise from one workload to another. It does not make the deployment risk-free, because the guest kernel, virtual machine monitor, agent, image, and management path still form an attack surface.&lt;/p&gt;

&lt;p&gt;The Kata project describes its architecture as hardware-virtualization-backed isolation with a dedicated kernel. That is a meaningful distinction from a namespaces-only design. It is also a reason to review the whole stack rather than treating a runtime class label as a trust decision.&lt;/p&gt;

&lt;h2&gt;
  
  
  The boundary moves
&lt;/h2&gt;

&lt;p&gt;In a shared-kernel runtime, a kernel vulnerability or an overbroad host capability can cross workload boundaries. A separate guest kernel gives the platform another layer to contain that class of failure. The guest still runs a kernel with its own vulnerabilities, and the hypervisor or virtual machine monitor is now part of the trusted computing base.&lt;/p&gt;

&lt;p&gt;The guest agent and the host-side runtime coordinator are privileged interfaces. A misconfigured mount, a guest image with unnecessary services, or an exposed management socket can create a path that does not depend on breaking the hypervisor. The isolation model must include those components and the identity that controls them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose it for a reason
&lt;/h2&gt;

&lt;p&gt;Kata is most relevant where the workload is untrusted, tenants are mutually hostile, or the cost of a shared-kernel escape is high enough to justify extra operational work. It is not automatically the right choice for every service. Boot time, memory overhead, device support, observability, and image maintenance all change.&lt;/p&gt;

&lt;p&gt;The Kata community has also noted that a feature-rich guest can enlarge the attack surface. A confidential-container deployment can add attestation agents, image-pull paths, and protected-data components. More components can improve a security property while introducing more code that must be verified and patched. Treat the runtime profile as part of the application's secure configuration, not an opaque default.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operate the boundary
&lt;/h2&gt;

&lt;p&gt;Pin and inventory the guest kernel, runtime, hypervisor, guest image, and agent versions. Patch them as a unit and maintain a way to identify workloads using a vulnerable combination. Keep the guest image minimal and remove services that the workload does not need. Disable unused host devices and shared filesystem paths, and require explicit authorization for privileged observability.&lt;/p&gt;

&lt;p&gt;For confidential workloads, verify the attestation chain and the policy that consumes it. A valid attestation report proves something about the measured environment. It does not prove that the application inside that environment is securely configured. Record which team accepts the verifier policy and what happens when a measurement changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;p&gt;Virtualization raises the cost of some attacks. It does not protect data from a compromised application, a malicious administrator with equivalent authority, or a bug in the management plane. It also does not remove the need to isolate network identities, secrets, and storage. The practical question is whether the selected runtime class matches the tenant boundary and whether the components behind that class are maintained.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://katacontainers.io/" rel="noopener noreferrer"&gt;Kata Containers project overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://katacontainers.io/blog/kata-community-ptg-updates-october-2026/" rel="noopener noreferrer"&gt;Kata Containers, October 2026 community update&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://katacontainers.io/blog/kata-containers-with-cloud-hypervisor/" rel="noopener noreferrer"&gt;Kata Containers, Cloud Hypervisor integration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>katacontainers</category>
      <category>isolation</category>
      <category>confidentialcomputing</category>
    </item>
    <item>
      <title>Aerospike's RBAC Refresh Delay Matters During Revocation</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Thu, 19 Nov 2026 02:01:05 +0000</pubDate>
      <link>https://dev.to/kozhevniko/aerospikes-rbac-refresh-delay-matters-during-revocation-5bji</link>
      <guid>https://dev.to/kozhevniko/aerospikes-rbac-refresh-delay-matters-during-revocation-5bji</guid>
      <description>&lt;h1&gt;
  
  
  Aerospike's RBAC Refresh Delay Matters During Revocation
&lt;/h1&gt;

&lt;p&gt;Aerospike is a distributed database that can hold high-volume operational data and serve latency-sensitive applications. When security is enabled, its role model controls authentication, privileges, and access at cluster, namespace, and set scope. Those controls are useful only if the deployment enables them and understands when a revocation takes effect.&lt;/p&gt;

&lt;p&gt;An existing AutoPR count-only observation recorded 47 matches for &lt;code&gt;title="Aerospike"&lt;/code&gt; on October 3, 2026. The title-based count is a candidate inventory, not a claim that every database accepted unauthenticated access. No new query was executed for this article.&lt;/p&gt;

&lt;h2&gt;
  
  
  Security must be enabled explicitly
&lt;/h2&gt;

&lt;p&gt;Aerospike's documentation describes a &lt;code&gt;security&lt;/code&gt; section in &lt;code&gt;aerospike.conf&lt;/code&gt; as the configuration that enables access control. It also describes predefined roles, custom roles, users, LDAP, and PKI authentication modes. The important operational fact is that the database's behavior depends on configuration and edition. A title match cannot establish which path is active.&lt;/p&gt;

&lt;p&gt;The public documentation states that privilege checks occur when a connection is established and periodically during the connection's lifetime. The server parameter &lt;code&gt;privilege-refresh-period&lt;/code&gt; has a documented default of 300 seconds and can be changed at runtime. If an administrator revokes a role, a long-lived client connection may retain its prior view until the next check.&lt;/p&gt;

&lt;h2&gt;
  
  
  Interpreting the count
&lt;/h2&gt;

&lt;p&gt;The stored query was:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;title="Aerospike"&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The 47 result is not a vulnerability count, and it does not distinguish an internet-facing admin endpoint from a regular database service. The same product could be shielded by private networking, mTLS, or an application gateway.&lt;/p&gt;

&lt;p&gt;The deterministic search link is:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkFlcm9zcGlrZSI%3D" rel="noopener noreferrer"&gt;https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkFlcm9zcGlrZSI%3D&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Revocation without a false sense of completion
&lt;/h2&gt;

&lt;p&gt;When removing a user or reducing a role, close active sessions or wait through the documented refresh interval before declaring the access change complete. Verify from a new connection and from an existing client. If the application pools connections, remember that a pool may present a connection whose server-side privileges are still being refreshed.&lt;/p&gt;

&lt;p&gt;Review role scope against namespace and set boundaries. A read-write role that reaches every namespace is not equivalent to a set-scoped role. Confirm that operational tools, backup jobs, and monitoring agents use separate identities from application clients. Avoid the default administrative credential after bootstrap, and keep credential rotation separate from application deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operational evidence
&lt;/h2&gt;

&lt;p&gt;Collect authentication and authorization logs from the database and its clients. Retain the role change, the session close, and the verification connection as one change record. Test a denied operation after revocation and a successful login. That evidence tells the team whether the control worked for the affected identity and connection pattern.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;p&gt;RBAC is one layer of database security. TLS, storage encryption, backups, network policy, query-level application authorization, and data retention still need owners. The 300-second default refresh is not a vulnerability by itself. It is a behavior that changes the meaning of "access removed" for long-lived connections.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aerospike.com/docs/database/manage/security/rbac/" rel="noopener noreferrer"&gt;Aerospike access control with roles and permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aerospike.com/docs/database/learn/security/access-control/" rel="noopener noreferrer"&gt;Aerospike access control with LDAP and PKI&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aerospike.com/docs/kubernetes/manage/security/access-control" rel="noopener noreferrer"&gt;Aerospike Kubernetes access control&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkFlcm9zcGlrZSI%3D" rel="noopener noreferrer"&gt;ZoomEye count-only observation, &lt;code&gt;title="Aerospike"&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>aerospike</category>
      <category>rbac</category>
      <category>database</category>
    </item>
    <item>
      <title>gVisor changes the syscall boundary, but host access still matters</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Wed, 18 Nov 2026 22:24:18 +0000</pubDate>
      <link>https://dev.to/kozhevniko/gvisor-changes-the-syscall-boundary-but-host-access-still-matters-55in</link>
      <guid>https://dev.to/kozhevniko/gvisor-changes-the-syscall-boundary-but-host-access-still-matters-55in</guid>
      <description>&lt;h1&gt;
  
  
  gVisor changes the syscall boundary, but host access still matters
&lt;/h1&gt;

&lt;p&gt;gVisor is designed to reduce the host kernel surface exposed to a container. Its Sentry implements a Linux-compatible application kernel in userspace. Applications make system calls that the platform redirects to the Sentry rather than passing every request directly to the host. This changes the isolation model for untrusted workloads, but it does not make the surrounding host configuration irrelevant.&lt;/p&gt;

&lt;p&gt;The gVisor security model treats the sandbox like a defense layer similar to a virtual machine, while acknowledging that it still relies on the host operating system and platform for protection from hardware attacks. A container escape through the application kernel interface is one path. Access to a host service, mounted socket, management API, or shared GPU remains another path that can bypass the intended boundary.&lt;/p&gt;

&lt;p&gt;Platform choice affects the attack surface and performance. The KVM platform uses virtualization support. The systrap platform intercepts system calls through the host kernel and is useful inside VMs or hosts without virtualization. The platform is not an abstract guarantee. Record which platform the workload uses and test the same workload under the deployment configuration.&lt;/p&gt;

&lt;p&gt;Network mode deserves special attention. gVisor's network stack is implemented for security and isolation, but host networking deliberately trades some of that isolation for native performance. &lt;code&gt;--network=host&lt;/code&gt; is documented as less secure in the FAQ. A service that starts with host networking for debugging should not inherit that setting in production.&lt;/p&gt;

&lt;p&gt;GPU support is another exception. The gVisor documentation notes that GPU use has its own security model and should be understood before placing a device in a sandbox. A process with access to a GPU driver, device node, or vendor management interface can reach resources beyond ordinary files and sockets. Treat device exposure as a separate permission review.&lt;/p&gt;

&lt;p&gt;A deployment baseline should include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The runsc version and platform.&lt;/li&gt;
&lt;li&gt;Namespace, network, and device configuration.&lt;/li&gt;
&lt;li&gt;Mounted paths and host sockets.&lt;/li&gt;
&lt;li&gt;Service-account tokens and cloud metadata reachability.&lt;/li&gt;
&lt;li&gt;Resource limits for CPU, memory, processes, and file descriptors.&lt;/li&gt;
&lt;li&gt;A test that attempts to reach host management interfaces and sensitive files.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;gVisor is often paired with a container runtime and Kubernetes. In that arrangement, the pod specification, runtime class, node operating system, and host hardening all contribute. A pod with a hostPath mount can still read or modify host data even when its system calls are mediated by gVisor. A privileged helper or host network route can likewise defeat a clean sandbox specification.&lt;/p&gt;

&lt;p&gt;For incident response, separate evidence about the guest workload from evidence about the sandbox runtime. Check the Sentry and platform logs, the pod or container configuration, and the node's access-control state. Do not assume that a sandbox crash or a failed syscall proves compromise, and do not assume that successful mediation proves the workload was benign.&lt;/p&gt;

&lt;p&gt;The right use of gVisor is defense in depth. It makes a useful boundary for untrusted computation, but the operator must still remove unnecessary host paths, credentials, devices, and networks. Isolation is the result of the whole deployment, not a single runtime class.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://gvisor.dev/docs/architecture_guide/security/" rel="noopener noreferrer"&gt;gVisor security model&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://gvisor.dev/docs/architecture_guide/platforms/" rel="noopener noreferrer"&gt;gVisor platform guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://gvisor.dev/docs/architecture_guide/networking/" rel="noopener noreferrer"&gt;gVisor networking guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://gvisor.dev/docs/user_guide/gpu/" rel="noopener noreferrer"&gt;gVisor GPU support and security considerations&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
      <category>c10</category>
    </item>
    <item>
      <title>IPsec traffic selectors define negotiated policy, not reachable trust</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Wed, 18 Nov 2026 19:03:24 +0000</pubDate>
      <link>https://dev.to/kozhevniko/ipsec-traffic-selectors-define-negotiated-policy-not-reachable-trust-4kpb</link>
      <guid>https://dev.to/kozhevniko/ipsec-traffic-selectors-define-negotiated-policy-not-reachable-trust-4kpb</guid>
      <description>&lt;h1&gt;
  
  
  IPsec traffic selectors define negotiated policy, not reachable trust
&lt;/h1&gt;

&lt;p&gt;An IPsec tunnel is often drawn as a line between two gateways, with subnet labels on each side. The labels in configuration are traffic selectors. They tell the peers which source and destination addresses and protocols are allowed inside a security association. They do not create a general routing relationship, and they do not prove that every address behind a gateway is safe to reach.&lt;/p&gt;

&lt;p&gt;StrongSwan expresses these selectors through &lt;code&gt;local_ts&lt;/code&gt; and &lt;code&gt;remote_ts&lt;/code&gt;, with older configuration names such as &lt;code&gt;leftsubnet&lt;/code&gt; and &lt;code&gt;rightsubnet&lt;/code&gt;. The peers propose selectors during IKE negotiation. A gateway can narrow a broad remote proposal to the subnets it actually authorizes. Narrowing is a security feature when it reflects policy, but it can also produce confusing operational behavior: a client may have a route for a large network while the selected security association covers only a smaller prefix.&lt;/p&gt;

&lt;p&gt;A selector is a packet-matching rule for IPsec. It is not a replacement for firewall rules, application authentication, or route hygiene. A /16 selector that permits all protocols to a server subnet is a broad policy even if the tunnel is encrypted. If the application is an administrative API on one host and one port, the selector should reflect that intended scope where the peer and kernel support narrowing. The firewall should still reject unexpected ports and sources.&lt;/p&gt;

&lt;p&gt;Design reviews should compare four representations of the same connection: the IKE proposal, the configured selectors, the installed kernel policy, and the routes that carry traffic into the tunnel. A mismatch between them is common after a migration. One side may propose &lt;code&gt;0.0.0.0/0&lt;/code&gt; while the other narrows to a specific subnet. The tunnel may come up, yet only some applications work. More importantly, an unintended selector can expose a network segment that the team believed was outside the tunnel.&lt;/p&gt;

&lt;p&gt;Wildcard selectors deserve special attention. When a remote peer proposes all addresses, the local gateway should narrow that request to authorized local subnets and protocols. It should not accept the broad first proposal merely because the peer is a known business partner. The trust relationship is with the partner gateway, not every host that gateway can route. Logging the negotiated selectors helps teams detect when a proposal changes after a firmware update or a configuration rollback.&lt;/p&gt;

&lt;p&gt;NAT, &lt;code&gt;iptables&lt;/code&gt;, and forwarding rules add another layer. The kernel may apply policy-based routing for traffic that matches an IPsec policy. A change to the rule order, the routing table, or the source address can move traffic outside the expected association. Both peers should verify the installed policy, not only the IKE status. Test with exact source and destination pairs, include the protocol and port, and check that an unselected destination fails rather than falling back to cleartext routing.&lt;/p&gt;

&lt;p&gt;Access control also depends on who can change selectors. A delegated network administrator who can add a broad subnet to a partner connection can enlarge the tunnel's effective reach. Treat selector changes like firewall changes: require a ticket, an owner, a security review for broad prefixes, and a post-change test. Keep a machine-readable inventory that maps connection names to expected selectors and owners. Alert when the installed policy differs from the approved baseline.&lt;/p&gt;

&lt;p&gt;IPsec is valuable because it gives a defined, negotiated security boundary. Traffic selectors are where that boundary becomes concrete for packets. They are not a statement that everything behind a gateway is trusted. A reliable deployment keeps selectors narrow, verifies what the kernel installed, and pairs the tunnel with routing and firewall rules that enforce the same intent.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.strongswan.org/docs/latest/howtos/forwarding.html" rel="noopener noreferrer"&gt;StrongSwan forwarding and split tunneling&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.strongswan.org/docs/latest/howtos/introduction.html" rel="noopener noreferrer"&gt;StrongSwan introduction&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/strongswan/strongswan/blob/master/man/ipsec.conf.5.in" rel="noopener noreferrer"&gt;StrongSwan ipsec.conf manual source&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ipsec</category>
      <category>networksecurity</category>
      <category>policy</category>
    </item>
    <item>
      <title>Java4Shell triage: identify reachable Base64 decoding paths</title>
      <dc:creator>kozhevniko</dc:creator>
      <pubDate>Wed, 18 Nov 2026 15:43:44 +0000</pubDate>
      <link>https://dev.to/kozhevniko/java4shell-triage-identify-reachable-base64-decoding-paths-4mkc</link>
      <guid>https://dev.to/kozhevniko/java4shell-triage-identify-reachable-base64-decoding-paths-4mkc</guid>
      <description>&lt;h1&gt;
  
  
  Java4Shell triage: identify reachable Base64 decoding paths
&lt;/h1&gt;

&lt;p&gt;An affected Java runtime is a necessary condition for CVE-2026-114938. It is not sufficient evidence that an application is exploitable. The vulnerability becomes reachable when attacker-controlled Base64 data reaches the affected decoder while the AVX-512 VBMI intrinsic is active.&lt;/p&gt;

&lt;p&gt;CISA calls the issue a critical Java memory-corruption flaw and urges immediate patching. Oracle gives it a CVSS 3.1 score of 8.1 with high attack complexity. That combination supports a fast response and a careful application-level assessment. Teams need to find both the JVM and the data path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common decode boundaries
&lt;/h2&gt;

&lt;p&gt;Red Hat lists HTTP Basic credentials, SAML artifacts, CSRF tokens, and MIME encoded words as examples of data routinely decoded by Java applications. JWTs, cookies, file upload formats, and protocol payloads can also carry Base64. The exact route depends on application code and libraries.&lt;/p&gt;

&lt;p&gt;Triage should begin with endpoints that decode data before authentication completes. Calif reported pre-authentication test chains in Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate. It also reported post-authentication chains in Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker. These are demonstrations against particular configurations, not proof that every deployment is exploitable.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to collect
&lt;/h2&gt;

&lt;p&gt;Map each internet-facing service to its process, container image, and actual JVM. Record the Java vendor, full build, CPU features on the executing node, and effective values for &lt;code&gt;UseBASE64Intrinsics&lt;/code&gt; and &lt;code&gt;UseAVX&lt;/code&gt;. Include applications with bundled runtimes and appliances that do not appear in a host package inventory.&lt;/p&gt;

&lt;p&gt;Then identify decode sinks. Source review can find direct &lt;code&gt;Base64.Decoder&lt;/code&gt; calls. Framework configuration, authentication libraries, and upload parsers may hide the call. Request logs can show Base64-shaped values, but the absence of a visible value does not prove a path is absent because logging may redact or omit it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mechanism and exploitation limits
&lt;/h2&gt;

&lt;p&gt;The bug occurs in the native intrinsic's tail handling. Malformed padding underflows an output-size calculation and produces an out-of-bounds heap write. The Java decoder may later reject the request, so an error response is not evidence that the process remained uncorrupted.&lt;/p&gt;

&lt;p&gt;VulnCheck found that repeated crafted input can reliably crash a vulnerable service, while RCE requires heap grooming and an address disclosure path tailored to the target. A WAF rule or Base64 length cap can reduce one reachable path without fixing the runtime defect. Other endpoints or application protocols may still reach the decoder.&lt;/p&gt;

&lt;h2&gt;
  
  
  Impact
&lt;/h2&gt;

&lt;p&gt;A crash can remove an authentication, collaboration, or delivery service. Heap corruption may disclose adjacent objects or enable code execution in the Java process. The attacker's reach then depends on the process identity, mounted credentials, network policy, and privilege separation around the application.&lt;/p&gt;

&lt;h2&gt;
  
  
  Affected products and scope
&lt;/h2&gt;

&lt;p&gt;Oracle lists affected Java SE and GraalVM builds. CERT-EU identifies OpenJDK fixes at 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1. OpenJDK-derived distributions follow their own release schedules and build names. Red Hat says standard OpenJDK 8 and 11 do not contain this vulnerable intrinsic, although Oracle separately lists the Java SE 8u511b33-perf build as affected.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exposure context
&lt;/h2&gt;

&lt;p&gt;A ZoomEye Search for product fingerprints associated with Confluence, Jira, Jenkins, Artifactory, Keycloak, and PingFederate returned 252,557 matches on November 18, 2026. The exact CVE filter returned 0. The Search count indicates a broad candidate population, not a list of vulnerable services. Runtime and data-flow checks remain necessary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Remediation and mitigations
&lt;/h2&gt;

&lt;p&gt;Patch the JVM and restart the application. Confirm that the replacement image or process uses the fixed build. During the transition, restrict unauthenticated access, validate Base64 input, enforce size limits, and disable the affected intrinsic where operationally acceptable.&lt;/p&gt;

&lt;p&gt;Track the response by decode path as well as by host. The most important asset is not simply a Java installation. It is a reachable service where untrusted input crosses from the network into the vulnerable native decoder.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.oracle.com/security-alerts/cspunov2026.html" rel="noopener noreferrer"&gt;Oracle Critical Security Patch Update, November 2026&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://content.govdelivery.com/accounts/USDHSCISA/bulletins/4332a87" rel="noopener noreferrer"&gt;CISA: Critical Java Vulnerability Requires Immediate Patching&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://access.redhat.com/security/vulnerabilities/RHSB-2026-018" rel="noopener noreferrer"&gt;Red Hat vulnerability bulletin RHSB-2026-018&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cert.europa.eu/publications/security-advisories/2026-021/" rel="noopener noreferrer"&gt;CERT-EU Security Advisory 2026-021&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://calif.io/java4shell/" rel="noopener noreferrer"&gt;Calif: Java4Shell technical disclosure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.vulncheck.com/blog/java4shell" rel="noopener noreferrer"&gt;VulnCheck: Java4Shell research observations&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>vulnerability</category>
      <category>java</category>
      <category>triage</category>
    </item>
  </channel>
</rss>
