[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cve-CVE-2026-21445":3,"landing-trending":52,"landing-articles":78},{"id":4,"cve_id":5,"euvd_id":6,"summary":7,"published":8,"cvss_data":9,"is_remote":10,"cwes":11,"cpes":13,"technologies":18,"references":21,"score":27,"epss_score":28,"epss_percentile":29,"is_kev":10,"cisa_kev_date_added":30,"cisa_kev_due_date":30,"cisa_ssvc":31,"attack_mappings":41,"exploits":48},10399,"CVE-2026-21445","EUVD-2026-0034","Langflow Missing Authentication on Critical API Endpoints\n\n### Summary\nMultiple critical API endpoints in Langflow are missing authentication controls, allowing any unauthenticated user to access sensitive user conversation data, transaction histories, and perform destructive operations including message deletion. This affects endpoints handling personal data and system operations that should require proper authorization.\n\n### Details\nThe vulnerability exists in three API endpoints within `src\u002Fbackend\u002Fbase\u002Flangflow\u002Fapi\u002Fv1\u002Fmonitor.py` that are missing the required `dependencies=[Depends(get_current_active_user)]` authentication dependency:\n\n**Affected Endpoints:**\n\n1. **GET `\u002Fapi\u002Fv1\u002Fmonitor\u002Fmessages`** (Line 61)\n   ```python\n   @router.get(\"\u002Fmessages\")  # ❌ Missing authentication\n   async def get_messages(\n       session: DbSession,\n       flow_id: Annotated[UUID | None, Query()] = None,\n       session_id: Annotated[str | None, Query()] = None,\n       # ... other parameters\n   ) -> list[MessageResponse]:\n   ```\n\n2. **GET `\u002Fapi\u002Fv1\u002Fmonitor\u002Ftransactions`** (Line 183)\n   ```python\n   @router.get(\"\u002Ftransactions\")  # ❌ Missing authentication\n   async def get_transactions(\n       flow_id: Annotated[UUID, Query()],\n       session: DbSession,\n       params: Annotated[Params | None, Depends(custom_params)],\n   ) -> Page[TransactionTable]:\n   ```\n\n3. **DELETE `\u002Fapi\u002Fv1\u002Fmonitor\u002Fmessages\u002Fsession\u002F{session_id}`** (Line 165)\n   ```python\n   @router.delete(\"\u002Fmessages\u002Fsession\u002F{session_id}\", status_code=204)  # ❌ Missing authentication\n   async def delete_messages_session(\n       session_id: str,\n       session: DbSession,\n   ):\n   ```\n\n**Inconsistency Evidence:**\nOther endpoints in the same file properly implement authentication:\n```python\n@router.get(\"\u002Fmessages\u002Fsessions\", dependencies=[Depends(get_current_active_user)])  # ✅ Properly secured\n@router.delete(\"\u002Fmessages\", status_code=204, dependencies=[Depends(get_current_active_user)])  # ✅ Properly secured\n```\n\n### PoC\nComplete reproduction steps to demonstrate the vulnerability:\n\n**Prerequisites:**\n1. Start a Langflow server instance\n2. Ensure no authentication headers or API keys are provided\n\n**Reproduction Commands:**\n```bash\n# 1. Access all user conversations without authentication\ncurl http:\u002F\u002Flocalhost:7860\u002Fapi\u002Fv1\u002Fmonitor\u002Fmessages\n\n# 2. Access transaction history without authentication\ncurl \"http:\u002F\u002Flocalhost:7860\u002Fapi\u002Fv1\u002Fmonitor\u002Ftransactions?flow_id=00000000-0000-0000-0000-000000000000\"\n\n# 3. Delete user messages by session without authentication\ncurl -X DELETE http:\u002F\u002Flocalhost:7860\u002Fapi\u002Fv1\u002Fmonitor\u002Fmessages\u002Fsession\u002F00000000-0000-0000-0000-000000000000\n```\n\n**Expected vs Actual Behavior:**\n- **Expected:** All requests should return `401 Unauthorized` \n- **Actual:** All requests return successful responses with sensitive data or perform destructive operations\n\n### Impact\n\n**Vulnerability Type:** Broken Authentication and Authorization (OWASP Top 10 - A01:2021)\n\n**Severity:** High\n\n**Who is Impacted:**\n- **All Langflow users**: Personal conversation data exposed to unauthorized access\n- **System administrators**: Transaction logs disclosed\n\n**Specific Impacts:**\n1. **Data Breach**: Unauthorized access to user conversations containing potentially sensitive personal information\n2. **Privacy Violation**: Transaction histories and user activity patterns exposed without consent\n3. **Data Destruction**: Malicious actors can delete user conversation histories without authorization\n4. **Compliance Risk**: Potential violations of data protection regulations (GDPR, CCPA, etc.)\n5. **System Intelligence**: Attackers can gather information about system usage patterns and user behavior\n\n**Attack Scenarios:**\n- Malicious users accessing proprietary conversation data\n- Malicious users deleting other users' conversation histories\n- Automated scraping of all user conversations for data harvesting\n- Reconnaissance attacks to understand system architecture and usage patterns\n\n**Recommended Fix:**\nAdd authentication dependencies to all affected endpoints:\n\n```python\n@router.get(\"\u002Fmessages\", dependencies=[Depends(get_current_active_user)])\n@router.get(\"\u002Ftransactions\", dependencies=[Depends(get_current_active_user)])\n@router.delete(\"\u002Fmessages\u002Fsession\u002F{session_id}\", dependencies=[Depends(get_current_active_user)])\n```\n\n**Environment:**\n- Langflow Version: Current main branch\n- Affected Components: API v1 monitoring endpoints\n- Authentication System: FastAPI dependency injection with `get_current_active_user`\n\n\u003Cimg width=\"1908\" height=\"1029\" alt=\"25-090901\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F44bd03b4-6ada-45b7-b81b-9cb83747172b\" \u002F>","2026-01-02T21:11:00Z",{},false,[12],"CWE-306",[14,15,16,17],"cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:*","cpe:2.3:a:langflow:langflow:1.7.0.dev44:*:*:*:*:*:*:*","cpe:2.3:a:langflow-base:langflow-base:0.6.9:*:*:*:*:*:*:*","cpe:2.3:a:langflow-base:langflow-base:*:*:*:*:*:*:*:*",[19,20],"Langflow Langflow","Langflow-Base Langflow-Base",[22,23,24,25,26],"https:\u002F\u002Fgithub.com\u002Flangflow-ai\u002Flangflow\u002Fcommit\u002F3fed9fe1b5658f2c8656dbd73508e113a96e486a","https:\u002F\u002Fgithub.com\u002Flangflow-ai\u002Flangflow\u002Fsecurity\u002Fadvisories\u002FGHSA-c5cp-vx83-jhqx","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-21445","https:\u002F\u002Fgithub.com\u002Flangflow-ai\u002Flangflow","https:\u002F\u002Fgithub.com\u002Flangflow-ai\u002Flangflow\u002Freleases\u002Ftag\u002F1.7.1",0,0.33289,0.98358,null,{"timestamp":32,"automatable":33,"tech_impact":34,"exploitation":35,"cisa_decision":36,"cisa_remediation_timeline":40},"2026-01-06T04:55:18.176919Z","yes","total","none",{"vector":37,"decision":38,"priority":39},"CISAv1\u002FE:N\u002FA:Y\u002FT:T\u002FM:H\u002F2026-10-26T07:02:57.452245\u002F","attend","medium","3D",[42],{"name":43,"source":44,"tactics":45,"technique_id":47},"Exploit Public-Facing Application","attack_vector",[46],"initial-access","T1190",[49,50],{"link":23},{"link":51},"https:\u002F\u002Fgithub.com\u002Fprojectdiscovery\u002Fnuclei-templates\u002Fblob\u002Fmain\u002Fhttp\u002Fcves\u002F2026\u002FCVE-2026-21445.yaml",{"count":53,"next":54,"previous":30,"results":55},266,"http:\u002F\u002Fweb:8606\u002Fapi\u002Ftrending_attacks\u002F?page=2&page_size=3&sorted_by=-published_at",[56,65,68],{"id":57,"title":58,"summary":59,"published_at":60,"severity":61,"vendor":62,"products":63},265,"Google Brotli decoder - Remote Code Execution via compressed requests (Exploitation Check)","This control is the second step of the Patrowl response to CVE-2026-111497 (Node2Shell). It complements the first control of 22 October 2026, which focused on the Node.js runtime, and does not replace it.\r\n\r\nWhy a second control\r\n\r\nCVE-2026-111497 is an out-of-bounds write in the Google Brotli decoder, the library that decompresses Brotli (\"br\") data. It was first published as a Node.js vulnerability, because Node.js bundles this decoder. Later publications showed that the flaw is in the library itself. Every product that embeds an affected version of the decoder is concerned, whatever its language or vendor. A public proof of concept demonstrates code execution.\r\n\r\nAny server that decompresses request bodies sent with \"Content-Encoding: br\" exposes the decoder to unauthenticated attackers. Known cases include Express 5 and NestJS 11 on Node.js, Koa and Fastify setups, Bun, Envoy and Istio with request decompression enabled, and any application or reverse proxy that decodes Brotli request bodies with an affected library.\r\n\r\nThe flaw also works in the other direction. A malicious server can compromise an unpatched client that decodes a Brotli response, for example Node.js fetch(), Python clients (requests, httpx, aiohttp, Scrapy) with the Brotli or brotlicffi package, or libcurl builds with Brotli support.\r\n\r\nWhat this control checks\r\n\r\nPatrowl sends small, valid Brotli-compressed requests to each asset and observes whether the server decodes them. The check does not depend on the technology: it detects the behaviour, whatever the stack behind it. These requests are what any legitimate client could send. They never reach the vulnerable code path and cannot affect the availability of the service.\r\n\r\nHow to read the result\r\n\r\nPotentially impacted means the asset decodes Brotli request bodies: the attack surface is exposed. It does not confirm that the asset is vulnerable. The version of the Brotli decoder in use is not visible from the outside.\r\n\r\nThis check covers applications that parse request bodies on their root path. A Not impacted result does not rule out exposure on other routes, nor on the client side. Checking the versions on the servers remains the only exhaustive verification.\r\n\r\nAffected and fixed versions\r\n\r\nGoogle Brotli 1.0.3 to 1.2.0 are affected, fixed in 1.0.10, 1.1.1 and 1.2.1. Fixed releases of the main products embedding it: Node.js 22.23.4, 24.22.1 and 26.12.1 (end-of-life lines 20.x and older and 25.x receive no fix), Bun 1.4.4, Envoy 1.37.8, 1.38.6, 1.39.3 and 1.40.0, Istio 1.29.9, 1.30.6 and 1.31.2, Python Brotli 1.2.1 and brotlicffi 1.2.1.0. Products that link against the system library depend on the Brotli package of the Linux distribution.\r\n\r\nRecommendations\r\n\r\nUpdate every component that embeds the Brotli decoder (only real fix). Start with the assets flagged by this control. Restart the processes after the update. Rebuild containers, single-executable applications and appliances that bundle an affected runtime or library.\r\n\r\nReduce the exposure until the update is deployed. Reject requests with \"Content-Encoding: br\" at the reverse proxy, load balancer or WAF, case-insensitively and including lists such as \"gzip, br\". On Envoy and Istio, disable request decompression for Brotli.\r\n\r\nReview outbound calls. List the features that fetch content from servers you do not control, and patch the services that host them first.","2026-10-24T10:37:22.192753Z",4,"google",[64],"brotli",{"id":53,"title":58,"summary":66,"published_at":60,"severity":61,"vendor":62,"products":67},"This control is the second step of the Patrowl response to CVE-2026-111497 (Node2Shell). It complements the first control of 22 October 2026, which focused on the Node.js runtime, and does not replace it.\r\n\r\nWhy a second control\r\n\r\nCVE-2026-111497 is an out-of-bounds write in the Google Brotli decoder, the library that decompresses Brotli (\"br\") data. It was first published as a Node.js vulnerability, because Node.js bundles this decoder. Later publications showed that the flaw is in the library itself. Every product that embeds an affected version of the decoder is concerned, whatever its language or vendor. A public proof of concept demonstrates code execution.\r\n\r\nAny server that decompresses request bodies sent with \"Content-Encoding: br\" exposes the decoder to unauthenticated attackers. Known cases include Express 5 and NestJS 11 on Node.js, Koa and Fastify setups, Bun, Envoy and Istio with request decompression enabled, and any application or reverse proxy that decodes Brotli request bodies with an affected library.\r\n\r\nThe flaw also works in the other direction. A malicious server can compromise an unpatched client that decodes a Brotli response, for example Node.js fetch(), Python clients (requests, httpx, aiohttp, Scrapy) with the Brotli or brotlicffi package, or libcurl builds with Brotli support.\r\n\r\nWhat this control checks\r\n\r\nPatrowl sends small, valid Brotli-compressed requests to each asset and observes whether the server decodes them. The check does not depend on the technology: it detects the behaviour, whatever the stack behind it. These requests are what any legitimate client could send. They never reach the vulnerable code path and cannot affect the availability of the service.\r\n\r\nHow to read the result\r\n\r\nPotentially impacted means the asset decodes Brotli request bodies: the attack surface is exposed. It does not confirm that the asset is vulnerable. The version of the Brotli decoder in use is not visible from the outside.\r\n\r\nThis check covers applications that parse request bodies on their root path. A Not impacted result does not rule out exposure on other routes, nor on the client side. Checking the versions on the servers remains the only exhaustive verification.\r\n\r\nTwo situations are possible. When the decoding is done by your own application or reverse proxy, identify the component and update it. If an update is not possible right away, reject requests with \"Content-Encoding: br\" at the reverse proxy or WAF.\r\n\r\nWhen the asset is hosted on a managed platform or behind a CDN (for example Platform.sh, Upsun or Fastly), the decoding may be done by the provider's edge router, in front of your application. You cannot patch it yourself, but this router handles all the traffic of your site. Ask your provider to confirm that its edge components are patched against CVE-2026-111497. Assets hosted on a managed platform or behind a CDN carry the tag \"paas: platform.sh\" or \"cdn: fastly\" in the asset view: for these assets, the Brotli decoding is done by the provider's edge router, in front of your application, and only the provider can patch it.\r\n\r\nAffected and fixed versions\r\n\r\nGoogle Brotli 1.0.3 to 1.2.0 are affected, fixed in 1.0.10, 1.1.1 and 1.2.1. Fixed releases of the main products embedding it: Node.js 22.23.4, 24.22.1 and 26.12.1 (end-of-life lines 20.x and older and 25.x receive no fix), Bun 1.4.4, Envoy 1.37.8, 1.38.6, 1.39.3 and 1.40.0, Istio 1.29.9, 1.30.6 and 1.31.2, Python Brotli 1.2.1 and brotlicffi 1.2.1.0. Products that link against the system library depend on the Brotli package of the Linux distribution.\r\n\r\nRecommendations\r\n\r\nUpdate every component that embeds the Brotli decoder (only real fix). Start with the assets flagged by this control. Restart the processes after the update. Rebuild containers, single-executable applications and appliances that bundle an affected runtime or library.\r\n\r\nReduce the exposure until the update is deployed. Reject requests with \"Content-Encoding: br\" at the reverse proxy, load balancer or WAF, case-insensitively and including lists such as \"gzip, br\". On Envoy and Istio, disable request decompression for Brotli.\r\n\r\nContact your edge provider about the status of the pathing (Fastly \u002F Plateform.sh)\r\n\r\nReview outbound calls. List the features that fetch content from servers you do not control, and patch the services that host them first.",[64],{"id":69,"title":70,"summary":71,"published_at":72,"severity":61,"vendor":73,"products":74},263,"Oracle Java SE JSSE - Improper Access Control & Unauthorized Data Access & Unauthorized Data Modification","Oracle Java SE is the Java runtime and development platform. Its JSSE (Java Secure Socket Extension) component provides TLS\u002FSSL for secure network communication. Oracle GraalVM is a JDK distribution based on the same platform.\r\n\r\nCVE-2026-91403\r\n\r\nA vulnerability in the JSSE component of Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition can be exploited by an unauthenticated attacker with network access over multiple protocols. A successful attack can give unauthorized access to critical data and allow unauthorized creation, deletion or modification of data. It can also affect sandboxed Java Web Start applications and applets that run untrusted code. The record lists the weakness as CWE-284 (Improper Access Control) in the CISA ADP entry, while another database lists CWE-295. The record lists these affected versions:\r\n- Oracle Java SE: 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5, 27.0.1.\r\n- Oracle GraalVM for JDK: 17.0.21, 21.0.13.\r\n- Oracle GraalVM Enterprise Edition: 21.3.20.\r\n\r\nOracle published an out-of-cycle Security Alert on October 21, 2026. One secondary source says the fix makes Java distrust eight compromised intermediate CA certificates shipped with the JDK. The Oracle-focused sources do not confirm this root cause, so check it against the Oracle advisory. CISA ADP SSVC data shows Exploitation: none, Automatable: yes, Technical Impact: total. The CVE is not in the CISA KEV catalog as of October 22, 2026, and its EPSS score is below 1%.","2026-10-23T14:12:32.871954Z","Oracle",[75,76,77],"Oracle Java SE","Oracle GraalVM Enterprise Edition","Oracle GraalVM for JDK",{"count":79,"next":80,"previous":30,"results":81},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[82,90,98],{"id":83,"title":84,"summary":85,"published_at":86,"type":87,"link":88,"image_url":89},30,"PHP2Shell: Two Critical RCE Flaws in PHP (CVSS 9.2)","Unauthenticated code execution demonstrated on WordPress, Drupal and Joomla, and reproduced in our lab. Patched versions and steps to take today.","2026-10-22T00:00:00Z","cve","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fphp2shell-2-critical-rce-flaws-php-cvss-9-2","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002Fc0615c4ee6-1792684469\u002Fphp2shell-2-critical-rce-flaws-php-cvss-9-2.png",{"id":91,"title":92,"summary":93,"published_at":94,"type":95,"link":96,"image_url":97},29,"Manage External Security Across All Your Entities","Centralize the management of entities, users and external security resources while maintaining strict data isolation with Patrowl.","2026-09-15T00:00:00Z","security tips","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fmulti-entity-external-security-how-structure-governance-group-level","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F8b2c0cc5eb-1789551467\u002Fvisu_1_multi_tenancy_dark_1x.webp",{"id":99,"title":100,"summary":101,"published_at":102,"type":103,"link":104,"image_url":105},28,"Will AI Become the Next Hacker? Bruce Schneier Answers at DEF CON 34","Tax law, finance, legislation: Bruce Schneier shows how AI could hack human rule systems just as easily as it hacks software.","2026-09-14T00:00:00Z","hacks","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fbruce-schneier-def-con-34","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F5c616d9db4-1789462598\u002Fai-hacker.en.png"]