Security Digest: June 10, 2026 - 18 Critical Vulnerabilities

Today’s alert is broad and urgent: critical flaws span Spring ecosystem components, Espressif IoT firmware, WordPress, OpenEMR, Pipecat, LMDeploy, and Ansible. Several issues enable remote code execution, data exposure, privilege escalation, or denial of service with low attacker effort.

· 12 min read

Executive Summary

Today’s alert is broad and urgent: critical flaws span Spring ecosystem components, Espressif IoT firmware, WordPress, OpenEMR, Pipecat, LMDeploy, and Ansible. Several issues enable remote code execution, data exposure, privilege escalation, or denial of service with low attacker effort.

Action required now: patch exposed internet-facing services first, disable risky features where immediate upgrades are not possible, and verify whether any affected versions are in production, CI/CD, or embedded device fleets.

Critical Vulnerabilities

  • CVE-2026-45328: Espressif ESF-IDF secure-services wrapper flaw
    • Impact: Attackers may abuse insecure bridge calls into TEE-protected peripherals and security features.
    • Affected Systems: ESF-IDF 5.5.4 and 6.0.
    • Immediate Action: Treat as high priority for IoT fleets and firmware builds; identify devices built from affected SDK versions.
    • Mitigation: Upgrade to 5.5.5 or 6.0.1.
  • CVE-2026-41732: Spring for Apache Pulsar trusted-package bypass
    • Impact: Crafted headers may lead to unsafe type handling and deserialization exposure.
    • Affected Systems: 2.0.0-2.0.5, 1.2.0-1.2.17, 1.1.0-1.1.17.
    • Immediate Action: Review any Pulsar consumers/producers using header mapping.
    • Mitigation: Upgrade to a fixed release; remove overly broad trusted-package settings.
  • CVE-2026-53673: BuddyPress private message IDOR
    • Impact: Authenticated users can read, reply to, or delete other users’ private messages.
    • Affected Systems: BuddyPress 14.4.0.
    • Immediate Action: Restrict message API access and monitor for abnormal thread access.
    • Mitigation: Apply the vendor patch as soon as available; limit REST exposure.
  • CVE-2026-41717: Spring Data MongoDB SpEL injection
    • Impact: User-controlled query parameters may execute injected expressions.
    • Affected Systems: 5.0.0-5.0.5, 4.5.0-4.5.11, 4.4.0-4.4.14, 4.3.0-4.3.16, 4.2.0-4.2.15, 4.1.0-4.1.14, 4.0.0-4.0.15, 3.4.0-3.4.19.
    • Immediate Action: Audit all @Query methods using capture-all placeholders.
    • Mitigation: Upgrade immediately; remove user-controlled expression paths.
  • CVE-2026-41729: Spring Data REST JSON Patch SpEL injection
    • Impact: Malicious JSON Patch requests can inject expressions through map keys.
    • Affected Systems: 3.7.0-3.7.19, 4.3.0-4.3.16, 4.4.0-4.4.14, 4.5.0-4.5.11, 5.0.0-5.0.5.
    • Immediate Action: Disable JSON Patch on exposed endpoints if possible.
    • Mitigation: Patch and validate all map key handling.
  • CVE-2026-41731: Spring for Apache Kafka trusted-package prefix bypass
    • Impact: Attackers can push crafted headers that deserialize arbitrary JDK types.
    • Affected Systems: 4.0.0-4.0.5, 3.3.0-3.3.15, 3.2.0-3.2.13, 2.9.0-2.9.13, 2.8.0-2.8.11.
    • Immediate Action: Check all Kafka consumers using header mapping and Jackson deserialization.
    • Mitigation: Upgrade; tighten trusted-package allow-lists immediately.
  • CVE-2026-46517: LMDeploy hardcoded trust_remote_code
    • Impact: Supply-chain remote code execution via Hugging Face model loading.
    • Affected Systems: LMDeploy 0.12.3 and earlier.
    • Immediate Action: Stop using affected builds for untrusted models.
    • Mitigation: No public patch yet; disable remote code paths and isolate deployments.
  • CVE-2026-46518: OpenEMR stored XSS in prescription multiprint
    • Impact: Patient-controlled content can run JavaScript in a clinician’s session.
    • Affected Systems: OpenEMR prior to 8.0.0.1.
    • Immediate Action: Upgrade immediately and review portal-to-clinician workflows.
    • Mitigation: Patch to 8.0.0.1; restrict affected print features until upgraded.
  • CVE-2026-41003: Spring Security form-generation code execution risk
    • Impact: Malicious registration data may execute code in generated HTML forms.
    • Affected Systems: 5.7.0-5.7.23, 5.8.0-5.8.25, 6.3.0-6.3.16, 6.4.0-6.4.16, 6.5.0-6.5.10, 7.0.0-7.0.5.
    • Immediate Action: Review any app that customizes SAML or relying-party registration data.
    • Mitigation: Upgrade to a fixed release; sanitize all influenced values.
  • CVE-2026-3018: WordPress Newsletters plugin SQL injection
    • Impact: Unauthenticated attackers may extract sensitive database data.
    • Affected Systems: Newsletters plugin up to 4.13.
    • Immediate Action: Disable the plugin on public sites until patched.
    • Mitigation: Apply vendor update; restrict database access and review logs.
  • CVE-2026-41695: Spring Data Commons property path resource exhaustion
    • Impact: Attackers can trigger denial of service through expensive path resolution.
    • Affected Systems: 4.0.0-4.0.5, 3.5.0-3.5.11, 3.4.0-3.4.14.
    • Immediate Action: Rate-limit requests that accept user-controlled property paths.
    • Mitigation: Patch and add strict input bounds.
  • CVE-2026-41716: Spring Data Commons heap exhaustion via cache poisoning
    • Impact: Repeated attacker strings can fill memory and crash services.
    • Affected Systems: 2.7.0-2.7.19, 3.3.0-3.3.16, 3.4.0-3.4.14, 3.5.0-3.5.11, 4.0.0-4.0.5.
    • Immediate Action: Watch for memory growth and repeated unusual property lookups.
    • Mitigation: Upgrade; add request throttling and memory alerts.
  • CVE-2026-41728: Spring Data REST JSON Patch authorization bypass
    • Impact: Intermediate path segments may bypass write-access filtering.
    • Affected Systems: 3.7.0-3.7.19, 4.3.0-4.3.16, 4.4.0-4.4.14, 4.5.0-4.5.11, 5.0.0-5.0.5.
    • Immediate Action: Disable JSON Patch where feasible.
    • Mitigation: Upgrade and re-test entity-level authorization controls.
  • CVE-2026-44716: Pipecat dev runner path traversal
    • Impact: Unauthenticated attackers can read arbitrary files accessible to the process.
    • Affected Systems: Pipecat 0.0.90 through 1.1.x before 1.2.0.
    • Immediate Action: Do not expose the development runner to untrusted networks.
    • Mitigation: Upgrade to 1.2.0; restrict access and remove the --folder endpoint from public use.
  • CVE-2026-45541: ESF-IDF WebSocket handshake crash
    • Impact: A malformed header can crash the server before authentication.
    • Affected Systems: 5.2.6, 5.3.5, 5.4.4, 5.5.4, 6.0.
    • Immediate Action: Prioritize internet-facing embedded services and gateways.
    • Mitigation: Upgrade to 5.2.7, 5.3.6, 5.4.5, 5.5.5, or 6.0.1.
  • CVE-2026-40988: Spring Security SAML REDIRECT binding DoS
    • Impact: Compressed SAML payloads can exhaust memory.
    • Affected Systems: 5.7.0-5.7.23, 5.8.0-5.8.25, 6.3.0-6.3.16, 6.4.0-6.4.16, 6.5.0-6.5.10, 7.0.0-7.0.5.
    • Immediate Action: Check SSO endpoints for REDIRECT binding exposure.
    • Mitigation: Patch and limit oversized SAML requests at the edge.
  • CVE-2026-40993: Spring Security SAML metadata deserialization risk
    • Impact: Malicious serialized payloads may be stored in the metadata repository.
    • Affected Systems: Spring Security 7.0.0 through 7.0.5.
    • Immediate Action: Restrict database write access immediately.
    • Mitigation: Patch; verify no untrusted actors can write to saml2_asserting_party_metadata.
  • CVE-2026-11837: ansible.posix authorized_key local privilege escalation
    • Impact: Local users may redirect file ownership changes to gain elevated access.
    • Affected Systems: ansible.posix authorized_key module deployments run as root.
    • Immediate Action: Stop running affected tasks on hosts with untrusted local users.
    • Mitigation: Update the collection; avoid symlink-unsafe key management until patched.

Previously Alerted

What to Do Now

  1. Patch the Spring stack first across apps using Spring Security, Spring Data Commons, Spring Data REST, Spring Data MongoDB, Pulsar, and Kafka.
  2. Inventory IoT and embedded builds for affected Espressif ESF-IDF versions and schedule firmware updates immediately.
  3. Disable or isolate risky features such as JSON Patch, SAML REDIRECT bindings, exposed dev runners, and public message APIs until fixed.
  4. Remove exposure by restricting internet access, adding WAF rules, and tightening trusted-package allow-lists.
  5. Verify installed versions in build manifests, container images, package locks, and firmware SBOMs.
  6. Monitor for memory spikes, repeated malformed requests, unexpected deserialization errors, and abnormal admin actions.

Verification Steps

  • Confirm package versions against vendor advisories and lockfiles.
  • Search for @Query, JSON Patch handlers, SAML endpoints, and Kafka/Pulsar header mappers.
  • Check whether any public-facing service accepts user-controlled property paths or map keys.
  • Review change logs for upgrades to 8.0.0.1, 1.2.0, 5.5.5, and 6.0.1.

Monitoring Recommendations

  • Alert on spikes in 4xx/5xx responses, memory growth, and process restarts.
  • Watch for unusual SSO or REST request patterns and repeated malformed headers.
  • Log and review access to private message threads, patient records, and metadata tables.

Related Resources

  • Internal: Add links to your Spring ecosystem incident playbook and embedded firmware patch tracker.
  • Official vendor advisories: Monitor Espressif, Spring, WordPress plugin maintainer, OpenEMR, Pipecat, LMDeploy, and Ansible release notes for fixed versions and guidance.

Keep reading