{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126644 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-126644 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126644 is a low-severity path traversal vulnerability in Red Hat Enterprise Linux 10, published on 12 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-126644 and fix it if it is affected.\n\nWhat it is: CVE-2026-126644 is a low-severity path traversal vulnerability in Red Hat Enterprise Linux 10, published on 12 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-126644 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Red Hat Enterprise Linux 10. 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-126644/ (Markdown: https://insights.sbomify.com/CVE-2026-126644/index.md)","id":"CVE-2026-126644","markdown":"https://insights.sbomify.com/CVE-2026-126644/index.md","name":"CVE-2026-126644","record":{"aliases":["GHSA-396m-42gr-rgx7"],"analysis":{"component_type":"developer_tool","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible collection","requires_auth":"low_privilege","requires_specific_call":false,"summary":"A local user can plant a symlink so the authorized_key module writes or changes permissions in an attacker-chosen directory when run as root.","user_interaction":"required","vuln_class":"path_traversal","vulnerable_functions":["_safe_open_write()","atomic_move()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"redhat","cpe":[],"cvss":{"score":3.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"A link-following flaw was found in the authorized_key module of the ansible.posix collection, residual to the fix for CVE-2026-11837. That fix guards only the final path component (os.chown with follow_symlinks=False and O_NOFOLLOW in _safe_open_write()). When an unprivileged local user replaces their ~/.ssh directory with a symlink to a directory they do not own, and an operator subsequently runs the authorized_key task as root (a common provisioning pattern), the module resolves its path operations through the symlink: atomic_move() writes the temporary file in the symlink target and renames it to \u003ctarget\u003e/authorized_keys, creating or overwriting a file in the attacker-chosen directory, and os.chmod(sshdir, 0o700) follows the symlink and changes the target directory's permissions. The written file is chowned to the unprivileged user, so this is not a privilege escalation, but it allows an attacker to create or overwrite files (for example in /etc/apt/apt.conf.d/, which APT reads regardless of file ownership) to cause integrity and availability impacts.","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":"Ansible.posix: authorized_key module follows a parent-directory symlink allowing writes outside the intended directory","id":"CVE-2026-126644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys","id":"CVE-2026-126658"},"nickname":null,"packages":[],"prev":{"headline":"Aap-gateway-operator: resource-server secret exposed in plaintext in the automationcontroller custom resource","id":"CVE-2026-126643"},"products":["Red Hat Enterprise Linux 10","Red Hat Enterprise Linux 9"],"published":"2026-11-12","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["Red Hat"]},"summary":"A local user can plant a symlink so the authorized_key module writes or changes permissions in an attacker-chosen directory when run as root.","url":"https://insights.sbomify.com/CVE-2026-126644/"}