{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102081 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102081 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102081 is a high-severity denial of service vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102081 and fix it if it is affected.\n\nWhat it is: CVE-2026-102081 is a high-severity denial of service vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102081 in the wild and no public exploit code.\n\nAffected product: Juniper Networks Junos OS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102081/ (Markdown: https://insights.sbomify.com/CVE-2026-102081/index.md)","id":"CVE-2026-102081","markdown":"https://insights.sbomify.com/CVE-2026-102081/index.md","name":"CVE-2026-102081","record":{"aliases":["GHSA-qf46-hrxr-5282"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Juniper Junos OS","requires_auth":"none","summary":"An unauthenticated attacker can cause a memory leak and subsequent denial of service on Juniper SRX and MX devices by generating high session churn when specific application services are enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:U/RE:M","version":"4.0"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"A Missing Release of Memory after Effective Lifetime vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a complete Denial-of-Service (DoS).\n\nOn SRX4000 Series, and SRX5000 Series with SPC3, and MX Series with SPC3, when one or more specific application services like ALGs, IDP/DPI, APPID, SECINTEL, AAMW or AppQoE are configured, a high connections per second churn will cause PFE memory to leak. If the memory is exhausted traffic processing will be impacted.\n\nUse the CLI command show security monitoring to monitor the memory utilization of the PFEs on the FPCs.\n\nThis issue affects Junos OS on SRX Series and MX Series:\n\n  *  23.4 versions from 23.4R2-S3 before 23.4R2-S7;\n  *  24.2 versions from 24.2R2 before 24.2R2-S3;\n  *  24.4 versions before 24.4R2-S3;\n  *  25.2 versions before 25.2R1-S2, 25.2R2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in Junos OS","id":"CVE-2026-102081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: SRX Series: If TLS session resumption is configured and a specific TLS message is received a PFE crash occurs","id":"CVE-2026-102082"},"packages":[],"prev":{"headline":"Junos OS: MX Series: Malformed SyncE or PTP clock input causes continuous RE switchover","id":"CVE-2026-102080"},"products":["Junos OS"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["Juniper Networks"]},"summary":"An unauthenticated attacker can cause a memory leak and subsequent denial of service on Juniper SRX and MX devices by generating high session churn when specific application services are enabled.","url":"https://insights.sbomify.com/CVE-2026-102081/"}