{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-21919 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21919 is a high-severity vulnerability in Juniper Junos, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21919 and fix it if it is affected.\n\nWhat it is: CVE-2026-21919 is a high-severity vulnerability in Juniper Junos, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21919 in the wild and no public exploit code.\n\nAffected product: Juniper Junos. 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-21919/ (Markdown: https://insights.sbomify.com/CVE-2026-21919/index.md)","id":"CVE-2026-21919","markdown":"https://insights.sbomify.com/CVE-2026-21919/index.md","name":"CVE-2026-21919","record":{"aliases":["GHSA-qv89-vxpv-h7vc"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Juniper network OS","requires_auth":"low_privilege","summary":"A race condition in Junos OS management daemon allows attackers to cause a denial of service by rapidly connecting and disconnecting NETCONF sessions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos","vendor":"juniper"},{"product":"junos_os_evolved","vendor":"juniper"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/AU:Y/R:U/RE:M","version":"4.0"},"cwes":[{"id":"CWE-821","name":"Incorrect Synchronization"}],"description":"An Incorrect Synchronization vulnerability in the management daemon (mgd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based attacker with low privileges to cause a complete Denial-of-Service (DoS) of the management plane.\n\nWhen NETCONF sessions are quickly established and disconnected, a locking issue causes mgd processes to hang in an unusable state. When the maximum number of mgd processes has been reached, no new logins are possible. This leads to the inability to manage the device and requires a power-cycle to recover.\n\nThis issue can be monitored by checking for mgd processes in lockf state in the output of 'show system processes extensive':\n\nuser@host\u003e show system processes extensive | match mgd\n\u003cpid\u003e root         20    0   501M  4640K lockf    1   0:01   0.00% mgd\n\nIf the system still can be accessed (either via the CLI or as root, which might still be possible as last resort as this won't invoke mgd), mgd processes in this state can be killed with 'request system process terminate \u003cPID\u003e' from the CLI or with 'kill -9 \u003cPID\u003e' from the shell. \n\nThis issue affects:\n\nJunos OS:\n\n  *  23.4 versions before 23.4R2-S4,\n  *  24.2 versions before 24.2R2-S1,\n  *  24.4 versions before 24.4R1-S3, 24.4R2;\n\nThis issue does not affect Junos OS versions before 23.4R1;\n\nJunos OS Evolved:\n\n  *  23.4 versions before 23.4R2-S5-EVO,\n  *  24.2 versions before 24.2R2-S1-EVO,\n  *  24.4 versions before 24.4R1-S3-EVO, 24.4R2-EVO.\n\nThis issue does not affect Junos OS Evolved versions before 23.4R1-EVO;","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":"Race condition in Junos OS","id":"CVE-2026-21919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos","juniper:junos_os_evolved"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: SRX Series: If a specific request is processed by the DNS subsystem flowd will crash","id":"CVE-2026-21920"},"packages":[],"prev":{"headline":"Junos OS: SRX and MX Series: When TCP packets occur in a specific sequence flowd crashes","id":"CVE-2026-21918"},"products":["Junos OS","Junos OS Evolved"],"published":"2026-04-09","related":[{"cvss_score":9.8,"headline":"Juniper Junos OS EX Series and SRX Series PHP External Variable Modification","id":"CVE-2023-36845","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":8.8,"headline":"Juniper Junos OS Path Traversal","id":"CVE-2020-1631","kev_date_added":"2022-03-25","published":"2020-05-04"},{"cvss_score":6.7,"headline":"Juniper Junos OS Improper Isolation or Compartmentalization","id":"CVE-2025-21590","kev_date_added":"2025-03-13","published":"2025-03-12"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36851","kev_date_added":"2023-11-13","published":"2023-09-26"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series PHP External Variable Modification","id":"CVE-2023-36844","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36846","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series Missing Authentication for Critical Function","id":"CVE-2023-36847","kev_date_added":"2023-11-13","published":"2023-08-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["Juniper Networks"]},"summary":"A race condition in Junos OS management daemon allows attackers to cause a denial of service by rapidly connecting and disconnecting NETCONF sessions.","url":"https://insights.sbomify.com/CVE-2026-21919/"}