{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-25-posix-wordexp-3-is-dangerous/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "[`wordexp(3)`](https://pubs.opengroup.org/onlinepubs/9799919799/functions/wordexp.html) is a POSIX API for performing shell-style expansions from C.\n\nIt's often cited/recommended as a way to do tilde expansion (e.g. `~/foo` to `/home/me/foo`):\n\n```c\n#include \n#include \n#include \n#include \n\nint expand_tilde(const char *input, char **output) {\n wordexp_t p;\n int ret = wordexp(input, &p, 0);\n if (ret == 0) {\n *output = strdup(p.we_wordv[0]);\n wordfree(&p);\n }\n return ret;\n}\n\nint main(void) {\n char *expanded = NULL;\n expand_tilde(\"~/foo\", &expanded);\n printf(\"expanded: %s\\n\", expanded);\n return 0;\n}\n```\n\nHowever, `wordexp(3)` is also dangerous! That last `0` argument is for the *flags* parameter. By default, all expansion features are enabled, **including command expansion**:\n\n```c\nexpand_tilde(\"$(whoami)/foo\", &expanded);\n```\n\nor:\n\n```c\nexpand_tilde(\"$(cat /etc/passwd)/foo\", &expanded);\n```\n\nDisabling this requires passing [`WRDE_NOCMD`](https://pubs.opengroup.org/onlinepubs/9799919799/functions/wordexp.html#:~:text=WRDE_NOCMD,Substitution%2C%20is%20requested.) as a flag. Unfortunately, this palliative at best in some libc implementations:\n\n- [musl implements `wordexp(3)`](https://git.musl-libc.org/cgit/musl/tree/src/misc/wordexp.c) by delegating to the system shell. It adds some perfunctory scanning for command substitutions before delegating, but fails to match some patterns that the underlying shell (like GNU Bash) can treat as valid command substitutions.\n\n- [macOS's libc implements `wordexp(3)`](https://github.com/apple-oss-distributions/Libc/blob/71bbe350ab79eef58113991d817ccc6165061a64/gen/FreeBSD/wordexp.c#L201) in a similar manner, delegating to `/usr/lib/system/wordexp-helper`[^1]. According to [Julian Squires](https://www.cipht.net) this had the same bypass as musl [as recently as 2023](https://www.cipht.net/2023/11/21/worried-by-wordexp.html), although I didn't bother testing whether it's still effective now that the default macOS shell is `zsh` instead of `bash`.\n\nBottom line: don't use `wordexp(3)` on untrusted inputs, even with `WRDE_NOCMD`.\n\n[^1]: Previously, macOS's `wordexp(3)` would shell out to Perl. `wordexp-helper` appears to be the \"modern\" solution.\n", "authors": [ "yossarian.net by yossarian" ], "captured_at": "2026-10-26T14:07:38.108821132+00:00", "category": "news", "content_html": "

wordexp(3) is a POSIX API for performing shell-style expansions from C.

\n

It's often cited/recommended as a way to do tilde expansion (e.g. ~/foo to /home/me/foo):

\n
#include <stdio.h>\n#include <stdlib.h>\n#include <string.h>\n#include <wordexp.h>\n\nint expand_tilde(const char *input, char **output) {\n    wordexp_t p;\n    int ret = wordexp(input, &p, 0);\n    if (ret == 0) {\n        *output = strdup(p.we_wordv[0]);\n        wordfree(&p);\n    }\n    return ret;\n}\n\nint main(void) {\n    char *expanded = NULL;\n    expand_tilde("~/foo", &expanded);\n    printf("expanded: %s\\n", expanded);\n    return 0;\n}\n
\n

However, wordexp(3) is also dangerous! That last 0 argument is for the flags parameter. By default, all expansion features are enabled, including command expansion:

\n
expand_tilde("$(whoami)/foo", &expanded);\n
\n

or:

\n
expand_tilde("$(cat /etc/passwd)/foo", &expanded);\n
\n

Disabling this requires passing WRDE_NOCMD as a flag. Unfortunately, this palliative at best in some libc implementations:

\n
    \n
  • \n

    musl implements wordexp(3) by delegating to the system shell. It adds some perfunctory scanning for command substitutions before delegating, but fails to match some patterns that the underlying shell (like GNU Bash) can treat as valid command substitutions.

    \n
    • \n
  • \n

    macOS's libc implements wordexp(3) in a similar manner, delegating to /usr/lib/system/wordexp-helper1. According to Julian Squires this had the same bypass as musl as recently as 2023, although I didn't bother testing whether it's still effective now that the default macOS shell is zsh instead of bash.

    \n
    • \n
\n

Bottom line: don't use wordexp(3) on untrusted inputs, even with WRDE_NOCMD.

\n
\n
    \n
  1. \n

    Previously, macOS's wordexp(3) would shell out to Perl. wordexp-helper appears to be the "modern" solution. ↩

    \n
    2. \n
\n
\n", "content_markdown": "[`wordexp(3)`](https://pubs.opengroup.org/onlinepubs/9799919799/functions/wordexp.html) is a POSIX API for performing shell-style expansions from C.\n\nIt's often cited/recommended as a way to do tilde expansion (e.g. `~/foo` to `/home/me/foo`):\n\n```c\n#include \n#include \n#include \n#include \n\nint expand_tilde(const char *input, char **output) {\n wordexp_t p;\n int ret = wordexp(input, &p, 0);\n if (ret == 0) {\n *output = strdup(p.we_wordv[0]);\n wordfree(&p);\n }\n return ret;\n}\n\nint main(void) {\n char *expanded = NULL;\n expand_tilde(\"~/foo\", &expanded);\n printf(\"expanded: %s\\n\", expanded);\n return 0;\n}\n```\n\nHowever, `wordexp(3)` is also dangerous! That last `0` argument is for the *flags* parameter. By default, all expansion features are enabled, **including command expansion**:\n\n```c\nexpand_tilde(\"$(whoami)/foo\", &expanded);\n```\n\nor:\n\n```c\nexpand_tilde(\"$(cat /etc/passwd)/foo\", &expanded);\n```\n\nDisabling this requires passing [`WRDE_NOCMD`](https://pubs.opengroup.org/onlinepubs/9799919799/functions/wordexp.html#:~:text=WRDE_NOCMD,Substitution%2C%20is%20requested.) as a flag. Unfortunately, this palliative at best in some libc implementations:\n\n- [musl implements `wordexp(3)`](https://git.musl-libc.org/cgit/musl/tree/src/misc/wordexp.c) by delegating to the system shell. It adds some perfunctory scanning for command substitutions before delegating, but fails to match some patterns that the underlying shell (like GNU Bash) can treat as valid command substitutions.\n\n- [macOS's libc implements `wordexp(3)`](https://github.com/apple-oss-distributions/Libc/blob/71bbe350ab79eef58113991d817ccc6165061a64/gen/FreeBSD/wordexp.c#L201) in a similar manner, delegating to `/usr/lib/system/wordexp-helper`[^1]. According to [Julian Squires](https://www.cipht.net) this had the same bypass as musl [as recently as 2023](https://www.cipht.net/2023/11/21/worried-by-wordexp.html), although I didn't bother testing whether it's still effective now that the default macOS shell is `zsh` instead of `bash`.\n\nBottom line: don't use `wordexp(3)` on untrusted inputs, even with `WRDE_NOCMD`.\n\n[^1]: Previously, macOS's `wordexp(3)` would shell out to Perl. `wordexp-helper` appears to be the \"modern\" solution.\n", "dateCreated": "2026-10-26T14:07:38.108821132+00:00", "date_created": "2026-10-25T15:09:29+00:00", "date_modified": "2026-10-25T15:09:29+00:00", "date_published": "2026-10-25T15:09:29+00:00", "description": "Comments", "external_url": "https://yossarian.net/til/post/posix-wordexp-3-is-dangerous/", "git": { "commit": "20068632b65d2830a2d54f25ca1d90d697bea2c0", "path": "items/lobste-rs/2026/10/2026-10-25-posix-wordexp-3-is-dangerous.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/20068632b65d2830a2d54f25ca1d90d697bea2c0/items/lobste-rs/2026/10/2026-10-25-posix-wordexp-3-is-dangerous.md" }, "id": "urn:aggr:item:ac69a322ac206bfce1edc19b4f0ce0d26bcbec80", "isBasedOn": { "@id": "https://yossarian.net/til/post/posix-wordexp-3-is-dangerous/" }, "mainEntity": { "@id": "https://yossarian.net/til/post/posix-wordexp-3-is-dangerous/", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-25-posix-wordexp-3-is-dangerous/#webpage" }, "author": [ { "@type": "Person", "name": "yossarian.net by yossarian" } ], "dateModified": "2026-10-25T15:09:29+00:00", "datePublished": "2026-10-25T15:09:29+00:00", "headline": "POSIX wordexp(3) is dangerous", "timeRequired": "PT2M", "url": "https://yossarian.net/til/post/posix-wordexp-3-is-dangerous/", "wordCount": 252 }, "name": "Archived snapshot: POSIX wordexp(3) is dangerous", "preview": null, "reading_minutes": 2, "replicated_at": null, "source": "lobste-rs", "source_name": "Lobsters: Top Stories of the Past Week", "summary": "Comments", "tags": [ "c", "security" ], "temporalCoverage": "2026-10-26T14:07:38.108821132+00:00", "title": "POSIX wordexp(3) is dangerous", "url": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-25-posix-wordexp-3-is-dangerous/", "word_count": 252 }